I love working with Claude Code in the terminal, but the workflow started getting ridiculous. Claude changes 6 files. I open Cursor/VS Code to figure out what changed. Find the suspicious hunk. Copy some code. Go back to Claude. Explain what I’m talking about. Repeat. Then I started running multiple agents and somehow my solution became… more terminal windows. 😂 So I built Stvena around the workflow I actually wanted. You start Claude normally with: stvena claude and Stvena stays around the agent as a review/control layer. Right now I can: see changed files and hunks while the agent works jump directly into the actual file select exact lines and send that context straight back to Claude run multiple Claude/Codex sessions inside the same Stvena window switch between those agents without opening another terminal configure my own keybindings once and keep them across projects connect Stvena to VS Code / Antigravity so the IDE follows what the agent is reading and changing live That last one has become my favorite. Claude is working in the terminal, but instead of staring at logs trying to imagine what’s happening, my editor follows along: agent opens file → IDE opens file agent moves through code → IDE follows agent changes code → I can see it Then if something looks wrong: review hunk → select exact lines → send them back → Claude continues No copying a diff into chat and then re-explaining the diff to the thing that created it. The way I’ve started thinking about it is: review should be a stream, not a ceremony after the agent finishes. Stvena is open source and still moving stupidly fast. GitHub: https://github.com/nccapo/stvena Website/demo: https://stvena.usectl.com/ I’m especially curious about people running Claude Code on larger repos: what part of reviewing/controlling an agent still forces you back into your IDE or another tool? I’ve already changed Stvena based on answers to that question, so hit me with the ugly workflows. submitted by /u/goddeschunk
Originally posted by u/goddeschunk on r/ClaudeCode