[MantisShrimp90]

(Neo)vim is setup wonderfully for this era. Im with Justin on the take that neovim can replace tmux soon literally all that is left is being able to restart terminal sessions on restart (which is even set as a goal for summer of code).

Neovim can already have all the agents running in different terminal buffers or there are plugins popping up every day to have deep integrations with your favorite or we even have some interesting harnesses that are unique to neovim like sidekick.

As always, the ability to compose small tools and edit any file allow neovim to stay relevant and more powerful than ever in my opinion while not forcing workflow changes like the others

[rstagi]

What you’re saying is super interesting, I’ve been using my setup for so long I might have missed some of the latest updates. I spend most of my time on TMUX with Claude Code and vim side by side btw, but I’m using it just to search some specific code and making small changes. I mostly review on GitHub PRs tbh

[MantisShrimp90]

Yea by having claude code in a terminal window within neovim rather than tmux you can leverage neovim commands to traverse, copy, paste and otherwise interact with the terminal window like any other buffer.

There are also plugins with more specific workflows but I like really seeing how much vanilla neovim can get done

[stvltvs]

Any tips on how to switch from Tmux to pure neovim?

[MantisShrimp90]

Knowing and leveraging the editor deeply is the best high level advice. Sessions for persistence, windows and buffers to manage screen real-estate (including terminals), and the terminal command itself to run the agentic workflow of your choice.

[qup]

I have one: don't.

Tmux is basically perfect software. It gets right out of your way.

It'll never come out of my development stack, or workflows.

Writing code isn't everything. Almost every time I start an apt command or something that might run a little while, I regret it if I'm not in a tmux session.

I could sooner do without vim than tmux.

[MantisShrimp90]

I will concede that this is the primary gap in the ecosystem right now is PERSISTENT terminal buffers but the act of doing terminal work in neovim is straight up nice if you use neovim motions to leverage that relationship.

Terminals resuming in a session is just a feature to be added not a complete functional rewrite.

[atmosx]

Vim (and the neo-thing) have multiple plugins that support vim-terminals but for agentic workflows tmux (a specialized tool) and similar tools (there are quite a few nowadays) are way better.