Sidekick.nvim is nice, you get a "real" terminal window on the side with many different agents to choose from.

Either opencode, claude, gemini, copilot, basically most that are relevant :D

Its a pretty light connection-layer, so it helps with sending context.

Ghostty split panes - coding TUI in one pane, neovim in the other, maybe a third pane for shell.

Just use this; it's literally claude code in a terminal tab in vim; also aware of what files are open in vim.

https://github.com/coder/claudecode.nvim

I just run them in separate terminals. The only real gap was that I couldn't tell the robot to open files in nvim when I wanted to look at them, the way it could in other IDEs, so I whipped up a quick skill (https://github.com/mkozlows/nvim-skill) to do that.

Check out avante.nvim: https://github.com/yetone/avante.nvim

Am I misremembering cause I could have sworn that Aider started out as a nvim plugin?? https://github.com/Aider-AI/aider

Mentioned elsewhere, but

:term claude

In a split goes a long way for me!

Just open a terminal split/tab and use claude there. The neovim buffer will update real-time.

Yes tab split, neovim on the left, companion on the right, or different tabs. The plugin codecompanion.nvim is also great. I use it for common tasks. Like:

vaf (visual around function) <space>ad (leader key add docstring).

And it documents the functions with my system prompt instructions for what good docstings should look like.

Use no plugins, install Zellij (or tmux) and use in split panes, works great.

CodeCompanion.nvim is a pretty nice plugin. I use that for quick stuff and opencode in the embedded terminal for larger tasks.

I just have vim open in one terminal tab and Claude Code open in another terminal tab. Works great.