agent-manager

Docs · Overview

Overview

agent-manager is a Go TUI that runs on top of tmux. Every agent you start is a real tmux session, so the manager is a window onto them rather than something they live inside. Quit it and they keep working.

Fig. 1the session list
The session list: twenty-odd agent sessions grouped under backend, its api subgroup, frontend and infra, each with a colour-coded live status, a real Claude Code transcript in the preview on the right, and machine gauges at the bottom left.
Twenty-three sessions, four projects, one nested subgroup. The preview is a real Claude Code pane.

The first run

There is no config to write and no daemon to start. Install it, then:

Terminal
agent-manager

The first launch, when no version has been stored yet, opens the first-run setup. It picks the agents, the layout, the density and the theme, walks the keys, and can import conversations the CLIs already saved. Settings keeps a row that walks through it again. Everything else you can change lives in Settings (s): the keys, the editor, the theme and the rest. Claude Code, OpenCode, Codex, Grok Build, Gemini CLI, Antigravity CLI, Pi, Command Code, Hermes Agent, Muse Code, Oh My Pi and Cursor CLI are built in, rules included, so there is nothing to describe before the first spawn.

KeyWhat it does
nNew session: name, tool, the model, effort and profile the tool offers, directory, optional saved prompts and a starting prompt, and a group.
gNew group.
spacePrompt the selected agent, or spawn one in the selected group.
CAdd an SSH connection, so another machine's sessions join the list.
?Every key, without leaving the app.

The mouse works on every screen. A click focuses a session, a double click folds a group, the wheel moves the cursor, a row drags by its ⠿ handle, […] opens a row's actions, and the divider between the list and the preview drags. The full-screen layout selects on a click and focuses on a double click.

Where the sessions live

Agent sessions run on a private tmux server named agentmgr, in the am_* namespace, so they never mix with the tmux you run yourself and a kill-server on your own socket leaves them alone. To reach one from a plain shell, name that server:

Terminal
tmux -L agentmgr ls
tmux -L agentmgr attach -t am_<id>
Inside a session ctrl+q detaches back to the manager when the terminal leaves it available; ctrl+\ is an alternate. ctrl+c reaches the agent while the session is focused, and the manager stays up. ctrl+r opens review and F3 opens the session's directory in your editor. These bindings are scoped to managed sessions, so they pass straight through everywhere else.

Where to go next

PageWhat it covers
InstallHomebrew, Scoop, the install script, the AUR, mise, Go, or a binary.
SetupThe first-run choices, the key tour, and bringing in conversations the CLIs already saved.
StatusWhy a row is orange, and where that verdict comes from.
Quick promptAnswering a blocked agent without attaching to it.
Review modeWhole-file diffs whose line comments go back to the agent.
SessionsWorktrees, shells, kill and revive, other machines, full screen.
KeysThe same keys the ? overlay shows.
MCPWhat an agent can do, and spawning from a script.
ConfigurationSettings, the key tables, the twelve built-in CLIs, saved prompts, and the themes.
EnvironmentsNamed environment profiles a session or a group launches under.
CommunityQuestions and setup help in #help and shared setups in #workflows, on the Agent Manager Community Discord. Bugs and features go in GitHub issues.