[nachocoll]

The friction of "launch agent, need shell in same directory, open new tab, cd back — fifty times a day" is the kind of micro-friction that compounds significantly in practice. The auto-snap workflow that detects the agent CLI and splits the pane automatically is a clean solution to a genuine ergonomic problem.

What's interesting about the AI coding CLI workflow space is that the tooling is evolving much faster than the mental models for using it well. The terminal is becoming a coordination surface — not just for running commands, but for managing the relationship between human attention and agent execution.

The Agile Vibe Coding Manifesto's concern with "automation remaining verifiable" is partly a terminal/observability problem: when the agent is running in a pane you can see, its actions are visible and interruptible. When it's a background process with only a text log, the accountability relationship degrades.

Curious how the chat panel that sends terminal output as context to the AI compares to just having the agent run in a pane you can see — that seems like the interesting design tension here: https://agilevibecoding.org

[tkjef]

i have found that the agent cli tools running in the panes are more dialed in by having the local directory structure as context and the best streaming text interface to show ai output on. the chat panel is kind of a nice to have as it's familiar. you can highlight text on the terminal > right click > choose Fix This|Explain This and it's sent to the chat panel to dig into more.

it's also, helpful for asking tangential questions about the current claude session, while allowing it to keep running but not interfering with it.