Hacker News Reader

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.

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.

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.

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.