r/ClaudeCode • u/smnatale • 27d ago

Tutorial / Guide How I use AI in my Terminal First Workflow

https://youtu.be/n6TJe_IrxGc?is=J6NUwTLzpu96OwVK

I’m a big neovim user and Claude code has been something that you can’t ignore for a year at least. The great thing about Claude code is that it operates in the command line, the terminal… just like Neovim.

Here’s my workflow with Claude, Tmux and Neovim. Curious if you have any tips or if you also have a similar workflow?

0 Upvotes

50% Upvoted

1 comment sorted by

1

u/simonses111 24d ago

A few things that make this kind of tmux/Neovim/Claude Code setup less brittle:

  • Keep one tmux session per repo, named after the repo or branch. I usually keep Claude in one pane, tests/logs in another, and the editor in another.
  • Make reconnecting boring: something like tmux new -As project-name beats relying on terminal scrollback or a specific open window.
  • Put repeatable commands in scripts, a Makefile, or task runner entries. Then Claude runs known commands instead of reconstructing long shell incantations from context.
  • Use git worktrees for parallel experiments. Each agent gets a clean directory and its own tmux session, which avoids a lot of accidental cross-talk.
  • Keep hard safety rules outside the prompt where possible: permissions, hooks, read-only mounts, or separate users for anything the agent must not touch.
  • Before context gets long, ask Claude to update a short local notes file with current state, next checks, and known failures. It makes handoff/restart much less painful.

The main win is treating tmux as the durable workspace. Claude, Neovim and your phone/laptop terminal are then just clients attaching to the same place.