Placeholder — screenshot: a sidebar of agent sessions across several repos, each with a brand avatar and status dot
Which agents
Nineteen CLIs are recognised on sight, by the command running in the pane:
Detection sees through the usual disguises: a full path, a
.cmd or .exe on
Windows, leading environment assignments, and an interpreter in front
(node .../claude/cli.js).
Your own wrapper
If you launch agents through a wrapper script, map its name to an agent inconfig.json:
claude,
codex, gemini, aider, amp, opencode, copilot, cursor, goose,
droid, pi, auggie, hermes, vibe, antigravity, grok, qwen,
omp, kimi).
What you get for free
Just by running an agent in a pane:Brand avatars
The tab chip and sidebar row show which agent runs where, so ten tabs stay
legible.
Git context
The branch and working-tree diff on the row, refreshed as the agent works.
Session resume
A pane lost to a reboot relaunches the conversation, carrying its original
flags. More →
Context feed
Palette commands that hand the current selection or the repo’s
git diff to
the running agent as a prompt.What needs a hook
Live status — working, needs your input, done — comes from the agent itself, over a channel tty7 installs into that agent’s configuration. It powers the status dots, the notifications, the tray icon, andtty7 wait.
Installing takes one click per agent under Settings → Agents.
Status and notifications →
Where to go next
Status and notifications
Hooks, status dots, the tray icon.
Sessions
Resume, fork, and copying a session id.
Orchestration
One agent driving another with
tty7 wait.