magenta.nvim

I wrote my own neovim AI harnesshttps://github.com/dlants/magenta.nvim And wrote about my thoughts on the relevance of nvim here https://dlants.me/ai-whiplash.html It's been many months, and I thoroughly prefer my harness inside of nvim as my day to day development environment. Using Claude code or cursor makes me feel very removed from the code. Exploring code, gathering context and tweaking prompts/giving guidance to the agent are very much enhanced by neovim. The biggest boon has been the fact that agents make customizing neovim a lot easier. Writing new bindings, config, and even building novel plugins. Here's a few that I built that fit into my workflow: - a tool for reviewing commits / branches / wip. https://github.com/dlants/glean - an iterative grepper https://github.com/dlants/shuck - a file picker that renders in your current w

Plugging away at my neovim AI plugin - https://github.com/dlants/magenta.nvim Recently added support for scripts (like Claude code workflows) and been iterating on the UI for that a bunch. I also ended up wanting other customized tooling - a more streamlined way to grep, find files and review code that my agent has written. So I wrote a few plugins for that : needle (finder with UI and sorting functions that suit me better), shuck (interactive grepper that has a workflow around refining grep commands) and glean (a review tool that lets you mark parts of the code as seen, leave comments, view diffs commit by commit or collapsed, etc). https://github.com/dlants/dotfiles/tree/main/nvim/lua These are all in various states of experimental and mostly just for me, but a few of my coworkers and friends have been using magenta and like it.

I've been developing an ai coding harness https://github.com/dlants/magenta.nvim for over a year now, and I use it (and cursor and claude code) daily at work. Fun observation - almost every coding harness (claude code, cursor, codex) uses a find/replace tool as the primary way of interacting with code. This requires the agent to fully type out the code it's trying to edit, including several lines of context around the edit. This is really inefficient, token wise! Why does it work this way? Because the LLMs are really bad at counting lines, or using other ways of describing a unique location in the file. I've experimented with providing a more robust dsl for text manipulation https://github.com/dlants/magenta.nvim/blob/main/node/tools/... , and I do think it's an improvement over just straight search/replace, but the agents do tend to str

For folks who use neovim, there's always https://github.com/dlants/magenta.nvim , which is just as good as claude code in my (very biased) opinion.

I've found these two to be really good https://github.com/dlants/magenta.nvim https://github.com/NickvanDyke/opencode.nvim

You can see a gif of it in the readme https://github.com/dlants/magenta.nvim?tab=readme-ov-file

I added next-edit-prediction to my neovim plugin. This was pretty interesting to implement! - I used an [lsp server](https://github.com/dlants/magenta.nvim/pull/162/files#diff-3...) to track opened files and aggregate text changes to get a stream of diffs. - I then feed that along with the [context surrounding the cursor](https://github.com/dlants/magenta.nvim/pull/162/files#diff-1...), and a [system prompt](https://github.com/dlants/magenta.nvim/pull/162/files#diff-a...) into an LLM, [forcing a tool use for a find/replace within the context window](https://github.com/dlants/magenta.nvim/pull/162/files#diff-1...) - Finally, I show the find/replace in the buffer using [virtual text extmarks](https://github.com/dlants/magenta.nvim/pull/162/files#diff-1...), applying a comment effect to the added sections, and a strikethrough to the removed

I recently finished some updates to my neovim ai plugin: - context tracking - multiple threads - compaction - sub-agents I decided to record a video of myself using the plugin to implement another feature. Aside from a demo of the plugin itself, I think it's a good view into what a typical workflow of using AI for development might look like, and I think is a good illustration of what these agents can and cannot currently do. Find out more here: https://github.com/dlants/magenta.nvim

neovim has AI integration! (and a pretty damn good one if I say so myself (I wrote it)) https://github.com/dlants/magenta.nvim

The interface for a provider does abstract over this, so you could implement it in the way that most other plugins do by rolling your own prompts and parsing: https://github.com/dlants/magenta.nvim/blob/main/node/provid... But yeah... it probably would take substantially more effort and be more brittle than having the model providers do it for you. I'm happy to accept PRs if folks want to go for it :)

I've been developing this on and off for a few weeks. There are a few videos on the README page showing demos of the plugin. I just shipped an update today, which adds: - inline editing with forced tool use - better pinned context management - prompt caching for anthropic - port to node (from bun) Check it out!