RSS Reader

Last updated: 2026-06-15 05:00 UTC

AddyOsmani.com

Agentic Code Review

14 Jun 2026

Agents made writing code almost free. Understanding it costs what it always did, which is why review is now the bottleneck. The 2026 data is strikingly consistent on this, and yet most advice about AI code review is wrong for most people, because a solo developer with no users and a team maintaining a ten-year-old application are not solving the same problem.

Loop Engineering

7 Jun 2026

You don't really need to be good at prompting anymore. The thing to get good at is the loop that does the prompting for you. It's five building blocks plus somewhere to keep notes, and Codex and Claude Code both have all five now.

The Intent Debt

5 Jun 2026

Technical debt lives in your code. Cognitive debt lives in your head. Intent debt lives in the artifacts you may have never wrote: the goals, constraints, and rationale for why the system is the way it is. If you're lucky, some of this exists scattered in team documents or discussions, but it's likely incomplete. It's the one kind of debt your agents can't pay down for you, and agentic engineering makes it the most expensive.

The Orchestration Tax

24 May 2026

Starting more agents is easy now. However, more agents running doesn't mean more of you available - your cognitive bandwidth doesn't parallelize. All the judgement to actually steer them and merge the code they write into the codebase still has to route through exactly one serial processor which is just you. Orchestration tax is basically the price you pay for forgetting this and the only real fix is to start architecting your own attention like you architect any concurrent system.

Don't Outsource the Learning

16 May 2026

Right now, it's too easy to let AI write the code while you skip the learning. The bug gets fixed. Your mental model doesn't move. We are silently trading future capability for present-day speed, and the tools won't force us to do otherwise. That part has to come from you.

Cognitive Surrender

5 May 2026

Cognitive offloading is delegating to the AI and still owning the answer. Cognitive surrender is when the AI's output quietly becomes your output and there is nothing left to check. For software engineers the line between the two moves under your feet most days, and most of us are crossing it without noticing.

Agent Skills

3 May 2026

AI coding agents take the shortest path to done, which usually means skipping the specs, tests, and reviews that make software reliable at scale. Agent Skills encodes those senior-engineer behaviors as workflows the agent has to follow, with anti-rationalization built in.

Long-running Agents

28 Apr 2026

A long-running agent can keep making progress over hours, days, or weeks. It can do this across many context windows and sandboxes, recover from failure, leave structured artifacts behind, and resume where it left off.

Agent Harness Engineering

19 Apr 2026

A coding agent is the model plus everything you build around it: prompts, tools, context policies, hooks, sandboxes, feedback loops. Harness engineering is the discipline of treating that scaffolding as a first-class artifact, and tightening it every time the agent slips.

Agentic Engine Optimization (AEO)

11 Apr 2026

AI coding agents consume documentation fundamentally differently from humans. If you're still optimizing only for human readers, you're leaving a growing share of your audience invisible to your tooling.

Matt Pocock

Learn anything with the /teach skill

8 Jun 2026

Can Cursor's HARDCORE Review Skill Stop The Slop?

28 May 2026

9 Things People Get Wrong With My /grill-* skills

25 May 2026

/handoff is my new favourite skill

21 May 2026

I stopped using /grill-me for coding. Here’s what I use instead:

14 May 2026

Anthropic's "dedicated monthly credit" is actually a huge cut

13 May 2026

New Skills! /handoff, /prototype, /review and /writing-* | Skills Changelog

12 May 2026

Burn through the backlog from hell with /triage

7 May 2026

I Open-Sourced My Own AFK Software Factory

30 Apr 2026

How To De-Slop A Codebase Ruined By AI (with one skill)

29 Apr 2026

LIVE: Watch me build a brand-new project from scratch

17 Apr 2026

Never Trust An LLM

27 Mar 2026

Claude Code tried to improve /init... Is it any better?

23 Mar 2026

Building a REAL feature with Claude Code: every step explained

18 Mar 2026

5 Claude Code skills I use every single day

16 Mar 2026

Anthropic Engineering Blog

How we contain Claude across products

25 May 2026

As agents grow more capable, so does their potential blast radius. The engineering question is how to cap it. Here’s what we’ve learned building containment for claude.ai, Claude Code, and Cowork.\n

An update on recent Claude Code quality reports

23 Apr 2026

We traced recent reports of Claude Code quality issues to three separate changes. Here's what happened and what we're changing.

Scaling Managed Agents: Decoupling the brain from the hands

8 Apr 2026

Harnesses encode assumptions that go stale as models improve. Managed Agents—our hosted service for long-horizon agent work—is built around interfaces that stay stable as harnesses change.

How we built Claude Code auto mode: a safer way to skip permissions

25 Mar 2026

Claude Code users approve 93% of permission prompts. We built classifiers to automate some decisions, increasing safety while reducing approval fatigue. Here's what it catches, and what it misses.\n

Harness design for long-running application development

24 Mar 2026

Harness design is key to performance at the frontier of agentic coding. Here's how we pushed Claude further in frontend design and long-running autonomous software engineering.

Eval awareness in Claude Opus 4.6’s BrowseComp performance

6 Mar 2026

Evaluating Opus 4.6 on BrowseComp, we found cases where the model recognized the test, then found and decrypted answers to it—raising questions about eval integrity in web-enabled environments.

Building a C compiler with a team of parallel Claudes

5 Feb 2026

We tasked Opus 4.6 using agent teams to build a C Compiler, and then (mostly) walked away. Here's what it taught us about the future of autonomous software development.

Quantifying infrastructure noise in agentic coding evals

5 Feb 2026

Infrastructure configuration can swing agentic coding benchmarks by several percentage points—sometimes more than the leaderboard gap between top models.\n\n

Designing AI-resistant technical evaluations

21 Jan 2026

What we learned from three iterations of a performance engineering take-home that Claude keeps beating.

Demystifying evals for AI agents

9 Jan 2026

The capabilities that make agents useful also make them difficult to evaluate. The strategies that work across deployments combine techniques to match the complexity of the systems they measure. \n

Effective harnesses for long-running agents

26 Nov 2025

Agents still face challenges working across many context windows. We looked to human engineers for inspiration in creating a more effective harness for long-running agents.

Introducing advanced tool use on the Claude Developer Platform

24 Nov 2025

We’ve added three new beta features that let Claude discover, learn, and execute tools dynamically. Here’s how they work.

Code execution with MCP: Building more efficient agents

4 Nov 2025

Direct tool calls consume context for each definition and result. Agents scale better by writing code to call tools instead. Here's how it works with MCP.

Beyond permission prompts: making Claude Code more secure and autonomous

20 Oct 2025

Claude Code's new sandboxing features, a bash tool and Claude Code on the web, reduce permission prompts and increase user safety by enabling two boundaries: filesystem and network isolation.

Equipping agents for the real world with Agent Skills

16 Oct 2025

Claude is powerful, but real work requires procedural knowledge and organizational context. Introducing Agent Skills, a new way to build specialized agents using files and folders.

Effective context engineering for AI agents

29 Sep 2025

Context is a critical but finite resource for AI agents. In this post, we explore strategies for effectively curating and managing the context that powers them.

A postmortem of three recent issues

17 Sep 2025

This is a technical report on three bugs that intermittently degraded responses from Claude. Below we explain what happened, why it took time to fix, and what we're changing.

Writing effective tools for agents — with agents

11 Sep 2025

Agents are only as effective as the tools we give them. We share how to write high-quality tools and evaluations, and how you can boost performance by using Claude to optimize its tools for itself.

Desktop Extensions: One-click MCP server installation for Claude Desktop

26 Jun 2025

Desktop Extensions make installing MCP servers as easy as clicking a button. We share the technical architecture and tips for creating good extensions.

How we built our multi-agent research system

13 Jun 2025

Our Research feature uses multiple Claude agents to explore complex topics more effectively. We share the engineering challenges and the lessons we learned from building this system.

Claude Code: Best practices for agentic coding

18 Apr 2025

Claude Code is a command line tool for agentic coding. This post covers tips and tricks that have proven effective for using Claude Code across various codebases, languages, and environments.

The \"think\" tool: Enabling Claude to stop and think in complex tool use situations

20 Mar 2025

A new tool that improves Claude's complex problem-solving performance

Raising the bar on SWE-bench Verified with Claude 3.5 Sonnet

6 Jan 2025

SWE-bench is an AI evaluation benchmark that assesses a model's ability to complete real-world software engineering tasks.

Building effective agents

19 Dec 2024

We've worked with dozens of teams building LLM agents across industries. Consistently, the most successful implementations use simple, composable patterns rather than complex frameworks.

Introducing Contextual Retrieval

19 Sep 2024

For an AI model to be useful in specific contexts, it often needs access to background knowledge.

AI Engineer

Why Can't Anyone Answer Questions About the Business? — Garrett Galow, WorkOS

11 Jun 2026

The agent-ready web: Simplify user actions with WebMCP — Tara Agyemang, Google

11 Jun 2026

Your Attention Is the Bottleneck, Not Your Agents — Zack Proser, WorkOS

11 Jun 2026

Stop Making Models Bigger, Make Them Behave — Kobie Crawford, Snorkel

10 Jun 2026

Sovereign Escape Velocity: Ownership w Open Models — Gus Martins, & Ian Ballantyne, Google DeepMind

10 Jun 2026

Self Driving Products: Product Signals to Pull Requests — Joshua Snyder, PostHog

10 Jun 2026

GPU Cloud Deployment Without Leaving Your IDE — Audry Hsu, RunPod

9 Jun 2026

RAG is dead, right?? — Kuba Rogut, Turbopuffer

9 Jun 2026

From Transcription to Live Music: Gemini's Audio Stack — Thor Schaeff, Google DeepMind

9 Jun 2026

2026 AI Engineer Vibe Reel

9 Jun 2026

Road to 5 Million Tokens: Breaking Barriers in Long Context Training — Max Ryabinin, Together AI

8 Jun 2026

Why More Context Makes Your Agent Dumber and What to Do About It — Nupur Sharma, Qodo

8 Jun 2026

Why Eval++ Is the Next Great Compute Primitive — Sunil Pai & Matt Carey, Cloudflare

8 Jun 2026

LLM Observability, Evaluation, Experimentation Platform — Dat Ngo, Arize

7 Jun 2026

Under 5 minutes to a deployed LLM endpoint — Audry Hsu, RunPod

7 Jun 2026

top scoring links : neovim

videre.nvim Complete Rewrite with Upgrades

12 Jun 2026

videre.nvim Complete Rewrite with Upgrades

Last year I released videre.nvim, a plugin that lets you explore JSON, YAML, and TOML in Neovim as a dynamic graph. It was a fun project, but the codebase resembled spaghetti. Adding features became a slog, and a bunch of things I wanted to build just weren’t possible with how the original version was structured.

So I did the only reasonable thing: I nuked it and rewrote the whole plugin from scratch.

The rewrite is finally done, and videre.nvim is in a much better place: cleaner internals, new features, and a way nicer editing experience overall.

Highlights

  • Full YAML and TOML editing support
  • Completely updated editing UI
  • New spacing options
  • New alignment settings
  • Settings validation (no more silent misconfigs)
  • Better highlighting API
  • More themes
  • General QoL improvements across the board
  • And most importantly: a codebase that doesn’t fight me every time I touch it

The plugin is actually moving again instead of being stuck under its own weight. If you tried the old version, this is a big upgrade. If you haven’t tried it yet, now’s a great time.

Repo: https://github.com/Owen-Dechow/videre.nvim

submitted by /u/BinaryBillyGoat
[link] [comments]

I love the frosted glass look with neovide & treesitter-context

11 Jun 2026

Released nvim 0.12.3

11 Jun 2026

features:
- :restart v:starttime, v:exitreason
- treat Lua string as "blob" in writefile()
- vim.treesitter. select()
- vim.pos: buf=0, pos.offset()
- `opts.scope` in `vim.ui.input`

fixes: LSP, ui2, vim.pos, vim.range, ...

https://github.com/neovim/neovim/commit/35b57441b0bac035dcfc591830e82abc560720b1

submitted by /u/chapeupreto
[link] [comments]

I made a small infographic about nvim's Regex lookarounds for fun and profit

12 Jun 2026

nvim-surround-wk — Which Key hints for nvim-surround

9 Jun 2026

nvim-surround-wk — Which Key hints for nvim-surround

Hi,

If you ever wanted to have Which Key hints for nvim-surround, my new plugin has got you covered. I have a lot of custom surrounds and found myself in need of this functionality (e.g., “How did I configure Markdown links again?”)

Enjoy

submitted by /u/Foo-Baa
[link] [comments]

libghostty-vt is about to replace libvterm inside Neovim, at last

9 Jun 2026

I saw this a while ago in this subreddit, but it appears that things have picked up fast and we're about to see it merged soon.

https://github.com/neovim/neovim/pull/39773

submitted by /u/CAPSLOCKAFFILIATE
[link] [comments]

diffs.nvim v0.4.0: THE all-in-one diff viewer for NeoVim

11 Jun 2026

diffs.nvim v0.4.0: THE all-in-one diff viewer for NeoVim

Hello peoples,

With the release of pierre-style diffs, my plugin diffs.nvim is now fleshed out. Whether you're a plain diff viewer or plugin author, diffs.nvim is the most comprehensive diff highlighter in the plugin ecosystem. See for yourself:

diffs.nvim v0.4.0: various diffing methods

Above are three diffing modes:

  1. Unified (botright): the classic "unified" diff that diffs.nvim pioneered, with stacked line numbers.
  2. Split (top): a unified &diff (builtin vimdiff) style split preview with custom highlight rendering and synchronized scrolling
  3. Stacked (botleft): like "unified", but see two line number columns according to the source and target, respectively.

As a recap, diffs.nvim is a robust and efficient diff viewer providing syntax highlighting to diffs. It's a must have if you use NeoGit, vim-fugitive, or want a more lightweight alternative to something like codediff.nvim.

Check it out here. As always, feel free to leave feedback.

I'm hoping to get treesitter-based diff highlighting in core in the coming months. This would mean you could see syntax highlighting on patch and git-diff style buffers natively, just by (likely) setting an option.

Lastly, I've learned a lot working on Neovim and learning from maintainers in recent months. Make sure to give them a shout-out for their consistency and hard work. Fun things ahead!

submitted by /u/barrettruth
[link] [comments]

Built a Neovim plugin for brainless-fast buffer switching: quickbuf.nvim

14 Jun 2026

Built a Neovim plugin for brainless-fast buffer switching: quickbuf.nvim

When I’m deep in a task, I keep bouncing between a small set of files.

I wanted something with near-zero thinking cost:

  • one-key label jump to buffers
  • pinned buffers for task-focused workflows
  • quick pinned cycling shortcuts
  • fast cleanup of unpinned noise

Inspired by flash.nvim and harpoon.nvim, I made QuickBuf.

Why QuickBuf

  • Fast one-key buffer switch (label -> buffer)
  • Pinned buffers = task focus (keep your working set tight)
  • Even faster pinned navigation with :QuickBufNextPinned / :QuickBufPrevPinned
  • Designed for brainless speed when context-switching a lot

Features

  • Ranked list: alternate buffer first, then pinned, then MRU
  • One-key jump labels
  • Batch pin/unpin (V + T)
  • Batch delete (V + d safe / D force)
  • Split/vsplit/tab open mode (s/v/t + label)
  • Fuzzy fallback on / (Snacks/Telescope/fzf-lua, or custom backend)
  • Clear all unpinned buffers quickly (c/C)
  • Optional devicons and highlight customization

Repo: https://github.com/tjgao/quickbuf.nvim

Would love for people to try it and share feedback/ideas.

submitted by /u/hornymoon
[link] [comments]

The magic of vim macros - 10 Examples

11 Jun 2026

The magic of vim macros - 10 Examples

In this video, I showcase 10 Vim macro examples that I've used throughout my programming journey. Some of them are truly awesome!

  1. Capitalize the First Letter of Each Line
  2. Capitalize the First Letter After a Period
  3. Convert a CSV List to a JSON Array
  4. Convert a Markdown List to HTML
  5. Add Line Numbers
  6. Convert a Log File to CSV
  7. Convert CSV Data to an SQL Script
  8. Convert Text to a Markdown TODO List
  9. The Primeagen's Best Macro
  10. Split Function Parameters
submitted by /u/NazgulResebo
[link] [comments]

packard.nvim — a security-first plugin manager built entirely on native `vim.pack`

8 Jun 2026

packard.nvim — a security-first plugin manager built entirely on native `vim.pack`

Hey, I used lazy.nvim forever. But, recently I became worried about supply chain attacks and how neovim/lazy can fall victim to it. I was also curious about the new native package manager (vim.pack). So, I built packard (pack + guard).

Every package update goes through a mandatory quarantine: fetch → 30-day cooldown → manual review (with optional inline AI diff analysis) → explicit approve/reject. Nothing installs without your say-so.

Built on native `vim.pack`, zero external dependencies, lazy.nvim-compatible specs, semver support, BYOK AI review, dependency resolution, and a full dashboard UI.

I've ran it daily with my 60+ plugins config, but would appreciate help debugging it.

https://github.com/ruicsh/packard.nvim

https://preview.redd.it/t985a286a46h1.png?width=2426&format=png&auto=webp&s=0f6d6344ad1fee5926bb644468ce45eca080227a

submitted by /u/PieceAdventurous9467
[link] [comments]

Tabterm.nvim – floating terminal with vertical tabs sidebar

11 Jun 2026

Tabterm.nvim – floating terminal with vertical tabs sidebar

I created this plugin for my own use, and it evolved in my dotfiles over several months. Today, I decided to split it into a separate repository and publish it. https://github.com/kremovtort/tabterm.nvim

submitted by /u/Nexmean
[link] [comments]

Fyler.nvim re-write done! with some breaking changes as expected.

13 Jun 2026

Fyler.nvim re-write done! with some breaking changes as expected.

Hello I am back again LOL!

Fyler.nvim core rewrite is completed and user can use it for their general uses and this time it will work without breaking in some common cases.

Release is not published yet! but i will publish it this sunday. I am preparing the github organization and transfer it there because there will be some other optional community asked extensions gonna live.

There are some missing features that I haven't been implemented yet but those feature will be there in a week or two because i haven't decided their flow yet.

If you wanna give me some advice on github organization then am all ears and you can access the rewrite here:

https://github.com/A7Lavinraj/fyler.nvim/tree/refactor/quality-of-life

Let me know what you think :)

submitted by /u/Lavinraj
[link] [comments]

Word dictionary using "dict"

13 Jun 2026

Word dictionary using "dict"

Just wanna share another addition to my config. I'm just bored.

``` local function define_word() local word = vim.fn.expand("<cword>") local buffer = vim.api.nvim_create_buf(false, true) local lines = nil

if vim.fn.executable('dict') == 0 then vim.notify("dict executable not found", "ERROR") return end

local command = vim.system({ "dict", word }, { text = true }):wait()

if command.code ~= 0 then print(command.stderr) return end

lines = vim.split(command.stdout, "\n", { plain = true }) vim.api.nvim_buf_set_lines(buffer, 0, -1, false, lines)

local window = vim.api.nvim_open_win(buffer, true, { relative = "cursor", bufpos = { 0, 0 }, border = "single", width = 90, height = 25, style = "minimal", title = word })

vim.api.nvim_create_autocmd("WinLeave", { buf = buffer, once = true, callback = function() vim.api.nvim_win_close(window, true) vim.bo[buffer].bufhidden = "wipe" end })

print("Dictionary", word) end

vim.keymap.set("n", "<leader>dc", define_word, { desc = "Dictionary" })

```

What it does is it creates a floating window for the definition of the word that's in the cursor. It's just a floating window for the output of dict <word> command.

submitted by /u/Handsome_oohyeah
[link] [comments]

cppman.nvim: C++ reference docs inside Neovim

14 Jun 2026

I hope it's okay that I post this here. If not, just let me know and I'll remove it.

I made a small Neovim plugin called cppman.nvim for browsing C++ reference docs directly inside Neovim.

I use it myself quite a bit, so I thought I'd share it in case anyone else finds it useful, or has ideas for improvements.

It adds :CPPMan, uses cppman's local index, and opens the docs in a floating buffer. It also supports both fzf-lua and snacks.nvim.

I tried to keep it lightweight and not too opinionated.

Repo: https://github.com/simonwinther/cppman.nvim

Stars are appreciated if you find it useful.

submitted by /u/BrilliantWishbone2
[link] [comments]

I made a plugin to render Oil metadata inside statuscol.nvim

11 Jun 2026

I made a plugin to render Oil metadata inside statuscol.nvim

📁 I've been using Oil for a long time and always felt a little friction from metadata being part of the editable buffer.

So I made this:

🔗 https://github.com/ergodice/statuscol-oil.nvim

✨ Features

  • 📋 Render Oil metadata inside statuscol.nvim
  • 🧹 Keep permissions, owners, sizes, icons, etc. outside the editable buffer
  • 🎯 Prevent accidental cursor movement into metadata fields
  • 👤 UID/GID display support
  • 📏 Configurable size formatting and width
  • 🛠️ A few additional QoL improvements

💭 Suggestions, feature requests, and feedback are very welcome!

submitted by /u/er-GOD-ic
[link] [comments]

I made a Rubik's cube for Neovim — and now it can teach you how to solve it

12 Jun 2026

I made a Rubik's cube for Neovim — and now it can teach you how to solve it

Tutorial Demo

I've been building rubiks-cube.nvim — a playable Rubik's cube in a floating window: isometric ASCII render, Singmaster-notation keys, timer with best-time tracking, and optional auto-solve via kociemba. The feature that finally made me want to share it: press t and it teaches you to solve the cube you actually scrambled, with the classic beginner layer-by-layer method — a side panel walks through eight stages (white cross → white corners → middle layer → … → done), each with a short explanation and the next move.

  • You can press n to let it make the move, or do the moves yourself.
  • If you make a different move instead, it re-plans from your new cube state.
  • No external binaries — the tutorial ships entirely in Lua.

Repo: https://github.com/xiangnongWu2233/rubiks-cube.nvim

Feedback welcome — especially from anyone who actually learns to solve the cube this way!

submitted by /u/GenX-Sealion-2233
[link] [comments]

Code minimaps always felt like low-signal UI, so I gave one a thermal scope. (gorbit99/codewindow.nvim

14 Jun 2026

A simple branch-aware scratchpad

8 Jun 2026

A simple branch-aware scratchpad

A lot of times I found myself losing my train of thought while switching between branches, so I just created nvim-scratchpad, a simple branch-aware scratchpad to take notes in markdown before I leave a branch.

https://github.com/grohith327/nvim-scratchpad/

submitted by /u/Fickle-Substance8283
[link] [comments]

minifugit.nvim - improved split view

12 Jun 2026

minifugit.nvim - improved split view

Hi guys!

Minifugit.nvim nightly version has an improved split diff view. It does not rely on the built in diff anymore, they are custom buffers with improved highlighting.

Try it if you find it interesting. Any feedback is welcome :)

submitted by /u/vieitesss_
[link] [comments]

New release: wiki.vim v0.12

13 Jun 2026

I've just finished a very long-standing issue: support for multi-line links. I think that warrants a new release (v0.12), so here you go: https://github.com/lervag/wiki.vim/releases/tag/v0.12.

wiki.vim is a Wiki plugin for Vim and neovim.

submitted by /u/lervag
[link] [comments]

How to figure out what Ctrl+i is doing in my neovim config?

12 Jun 2026

If I understand correctly, Ctrl+o and Ctrl+i are the default keybindings for going back and forward in the text position navigation history.

I'm regularly using Ctrl+o for going backwards, but Ctrl+i is not working. Depending on where I'm at, it either does not do anything, or jumps somewhere else, it seems like it's switching between tabs. So I'm not sure what it's bound to.
Although I do have this config, because I use Tab to switch between tabs:

vim.keymap.set('n', '<tab>', '<cmd>tabnext<cr>', { desc = 'Next Tab' }) 

But this should not affect Ctrl+i, right?

What would be a way to figure out why Ctrl+i is behaving this way, so what it is bound to? In my nvim config I could not find it being explicitly set up anywhere. I also cannot see it with the Telescope keymap finder (although I can't find Ctrl+o there either).
Or the easiest solution would be to explicitly set Ctrl+i in my config to jump forward in the navigation history? If yes, could someone tell me what the exact mapping for that would be?

UPDATE: it was clarified by multiple commenters that due to how terminal emulators handle the Tab key, a key mapping for Tab and Ctrl+i clashes. So the problem is caused by my config specifying a mapping for `<tab>`, that overrides the built-in Ctrl+i mapping.
A workaround was posted in this comment: https://www.reddit.com/r/neovim/comments/1u3qbil/comment/or7hsyd/, which for me works properly in Ghostty.

submitted by /u/DanielMurphy22
[link] [comments]

Are you using default keybindings for mini.surround?

9 Jun 2026

I find it a bit uncomfortable to hijack the default s keybind that is present in the Vim for a long time.

submitted by /u/4r73m190r0s
[link] [comments]

Release of matchparen.nvim v2

12 Jun 2026

matchparen.nvim https://github.com/monkoose/matchparen.nvim is alternative to built-in :h matchparen plugin.

Recently I have updated it to v2 It now uses coroutines internally to never block neovim UI. Not sure how it pressure the GC (have not tested it), but definitely not noticable. And cpu usage is usually lower than with built-in.

For anyone intrested why you should use it over built-in. You can try it with this example file https://gist.github.com/monkoose/b15955f48e9bf1d69f63e4b163ccd188

Just move the cursor (hold l/h) over curly braces on line 7. built-in plugin also has some bugs, where it highlights wrong pairs you can see it on line 31 inside the string.

It is definitely some extreme example, you are not usually edit such files. It just shows how faster and non-blocking it compare to built-in without benchmarks. And sometimes you do edit longline files and files with a lot of parentheses on a screen and when you do slowness of the built-in plugin is annoying.

submitted by /u/monkoose
[link] [comments]

Vim Appearances in Pop Culture?

9 Jun 2026

Just found a neat plugin for reusing VSCode workspace settings in Neovim: codesettings.nvim

14 Jun 2026

Disclaimer: I'm not affiliated with the author. I just found this plugin useful and wanted to share it

I recently found codesettings.nvim, and it solves a very practical problem I ran into: project-local LSP and formatter behavior.

My concrete use case was Go formatting. Some Go projects want plain gofmt, while others prefer gofumpt. I didn't want to enable gofumpt globally in my Neovim config, because that is really a per-project formatting decision.

With codesettings.nvim, a project can define local LSP settings in files like .vscode/settings.json, codesettings.json, or lspsettings.json, and Neovim can apply those settings through the LSP before_init flow.

That means one project can opt into gofumpt, while another project can keep using regular gofmt, without changing my global Neovim config.

What I like about it:

  • No nvim-lspconfig dependency
  • It keeps project-specific LSP settings out of global config
  • It makes formatter choices like gofumpt local to each project
  • Can reuse settings already present for VSCode users
  • It feels focused and lightweight

Compared with neoconf.nvim:

  • neoconf.nvim is more general-purpose, but it does not seem to be maintained very actively lately. it also still hard depends on old nvim-lspconfig
  • codesettings.nvim feels narrower in scope: load project-local settings and apply them to language servers. You have to apply them manually in before_init

Not saying everyone needs to switch, but for native LSP setups where project-local settings matter, this plugin feels really convenient.

submitted by /u/Asleep-Apartment6716
[link] [comments]