Agent-Manager: A Tmux TUI for Running Claude Code, Codex and OpenCode

Agent-Manager, a terminal user interface that runs multiple AI coding agents side by side in tmux sessions, has been released by developer YoanWai. The tool supports Claude Code, Codex, OpenCode, and Grok Build out of the box, letting users monitor, interact with, and revive sessions from a single list with live status and project tree organization. It is available via Homebrew, Go install, or GitHub Releases for macOS and Linux.

Run every AI coding agent from one terminal. Claude Code, Codex, OpenCode, and Grok run side by side, each in its own tmux session, so they keep working after you quit the manager. Instead of hunting through terminal tabs to see which agent is done and which is stuck, every session shows up in one list with live status, grouped into a project tree you can fold and reorder. You answer any of them without attaching: space sends a prompt straight into a session's pane, or spawns a new agent in the selected group. A dead session revives where it left off with v . And ctrl+r opens a full-file diff of what an agent changed, syntax-highlighted, where a comment you leave on a line goes straight back to the agent's pane. Status detection currently supports Claude Code , OpenCode , Codex , and Grok Build out of the box. Any other CLI tool can run as a session; add a tools.<name block with status rules to get live status for it see Configuration configuration . brew install yoanwai/tap/agent-manager Installs tmux with it if missing. go install github.com/YoanWai/agent-manager@latest Requires Go 1.26+ and tmux; installs to $ go env GOPATH /bin . Download from Releases https://github.com/YoanWai/agent-manager/releases macOS and Linux, amd64/arm64 . Run inside WSL2 https://learn.microsoft.com/windows/wsl/install : agent-manager lives on tmux, which is a Linux/macOS tool. In a WSL shell, install with Homebrew or grab the Linux binary from Releases. The manager checks GitHub Releases once a day and shows a ↑ vX.Y.Z available badge in the header when a newer version is out. Pull it in the way you installed: brew upgrade yoanwai/tap/agent-manager Homebrew go install github.com/YoanWai/agent-manager@latest Go agent-manager Sessions run inside tmux am namespace , so they survive the manager quitting. Inside a session, Ctrl+Q detaches back to the manager. agent-manager --version prints the version. | Key | Action | |---|---| n | New session name, tool, directory, optional starting prompt, group picker | g | New group name, parent, default path | enter | Attach session / fold group | ctrl+q | Inside a session: back to the manager | K / J or shift+↑ / shift+↓ | Reorder session or group among its visible siblings | m | Move session to another group | r | Rename session / edit tool; edit group name and default path | v | Revive a dead session revive command , e.g. claude --continue , resumes the conversation | a / u | Archive / restore a session, or a group and its entire subtree | d | Delete session, or a group + its entire subtree | space | Quick prompt: answer the selected session, or spawn an agent in the selected group | ctrl+r | Review the selected session's changes: full-screen whole-file diffs, line comments sent to the agent | f | Fold / unfold group | s | Settings quick-spawn tool, theme, review layout | t | Toggle archived view | e | Hide / show empty groups | / | Search | ? | Help | q | Quit sessions keep running | Press space to dock a prompt bar at the bottom of the sidebar. The target follows the cursor while the bar is open ↑↓ still navigate : - On a session row, enter sends the typed text straight into the session's pane, so the agent gets it as a user message without you attaching. The bar stays open and clears, ready for the next answer. - On a group row, enter spawns a new agent in that group with the prompt embedded, using the group's default path. The spawn tool starts at the Settings s default and tab cycles it claude ↔ opencode ↔ any configured tool ; the footer shows the current pick. The agent starts working on the prompt immediately. esc closes the bar. The new-session form's optional prompt field launches an agent the same way; tools whose CLI takes the prompt behind a flag declare it with prompt flag see Configuration configuration . Sessions spawned without a custom name every quick spawn, and the form with the name left blank get a placeholder like claude-a1b2 , and their first prompt opens by asking the agent to run agent-manager rename "<name " once with a short name for the broad feature of the session not a single subtask . The directive also tells the agent not to rename again unless you ask. When the first prompt cannot carry the directive a /slash command, or no prompt at all , the manager sends it as its own message once the tool's input box appears in the pane. The subcommand drops the name into a per-session file; the manager picks it up on the next poll and updates the sidebar row and the tmux status bar. This works with any tool, since it only needs the agent to read its prompt and run one shell command. Sessions you name yourself keep that name: the first prompt only notes that agent-manager rename is available later if you ask, and does not instruct the agent to rename now. You can still ask an agent to rename its session later, or run agent-manager rename yourself from a shell inside the session. A session's working directory is often an umbrella folder holding many repos, so review can only guess which one the agent means. An agent that knows which repo it is working in can say so by running agent-manager review-repo <path from a shell inside its session. The subcommand checks that the path is or sits inside a git repo, resolves it to the repo root, and drops it into a per-session file; the manager picks it up on the next poll and review opens on that repo the next time you open it. A path that is not inside a git repo is rejected, so a declaration is always a fact rather than a guess. An agent can also declare what its branch diffs against by running agent-manager review-base <ref from inside its worktree: the ref is validated in that repo, stored per session and repo, and the "vs target" scope uses it from then on. agent-manager review-base --clear returns to automatic detection. A stored ref that stops resolving surfaces as an error in review, and B opens a target picker the repo's branches plus an auto entry to set or clear it by hand. Agents usually work in git worktrees, one branch per worktree, and those worktrees can live anywhere on disk. A declared path that is a worktree root is accepted wherever it lives, so one review-repo call names both the repo and the branch under review. Review resolves its target in a fixed order: a repo you picked by hand with r or b wins for as long as the manager is running, then the agent's declared repo, then the ranking dirty working trees first, then most recent commit . When the picked or declared path stops being a git repo, review says so in the status line and r is there to pick the right one. Every session the manager spawns or revives carries the agent-manager MCP server, so MCP-capable agents see rename , review repo and review base as native tools with descriptions telling them when to call each: no prompt injection, no per-project setup. The server lives in the same binary agent-manager mcp , stdio and identifies the calling session through its environment. Registration is per tool. The built-in claude, codex, opencode and grok tools register automatically: claude gets a generated --mcp-config file, codex gets -c mcp servers... overrides, opencode gets an OPENCODE CONFIG merge file, and grok gets a one-time grok mcp add --scope user entry on its first launch. A custom tool opts in with mcp = "<style " in its config section, or out with mcp = "none" . The CLI subcommands keep working everywhere, MCP or not. Press ctrl+r on a session to open a full-screen review of its repo: changed files with +/− counts on the left, the whole file on the right with syntax highlighting and changed lines tinted, so every edit reads in full context. Arrow keys and ctrl+d / ctrl+u scroll the file, g / G jump to top and bottom, J / K or tab / shift+tab switch files, n / N jump between changes, u toggles unified and side-by-side, s cycles the scope uncommitted, vs target, last commit, staged , and space marks a file reviewed. When the working directory holds several repos, r opens a picker you type to filter, and b lists the current repo's worktrees by branch name so you can review another branch with one keypress. B picks the target the merge-into branch the "vs target" scope compares against. Each changeable value in the header wears its own key, so the scope, layout, repo, and target pills read as s , u , r , B legends at a glance. The diff refreshes as the agent keeps editing. Press c on a line to write a comment; C flattens every comment into one review prompt and sends it straight into the agent's pane, so the agent starts addressing your notes while you watch the diff update. esc closes the review. Groups are paths backend/api/auth forming a tree of unlimited depth. Sessions can live at any node, including the root. Create subgroups inline with g , reorder both groups and sessions with K / J or shift+↑↓ ; the order persists , fold a subtree with f , hide or restore empty groups visually with e , and edit a group's name and default path with r . On a session, r renames it and tab cycles the tool status rules and revive follow the new tool; useful when you quit one agent in the pane and start another . Each session's tmux pane is polled default every 2s to derive a status: | Status | Meaning | |---|---| working | The agent is busy on a turn | waiting | Blocked on you: a dialog, a permission ask, or a plain-text question | finished | Turn ended — an alert that clears to idle once you enter the session | errored | The tool reported an error | idle | Nothing running | dead | The tmux session is gone | Each row carries its status and tool inline, and a folded group keeps a count per status so a collapsed subtree still tells you whether anything needs you. Selecting a session shows the tail of its pane on the right, which is how a waiting agent's actual question reaches you without attaching. Detection matches per-tool regex rules against the visible pane, analyzes the newest turn to tell finished from waiting , and treats streaming output content changing between polls as working . A turn that ends without any turn-summary line still resolves: when a working pane goes quiet, the turn counts as finished , or waiting when it ends on a question. Polling keeps running while you are inside a session, so statuses stay live. The selected session's pane tail renders in the preview panel, and moving the cursor fetches the preview immediately. For Claude Code, status comes first-hand from hook events https://docs.anthropic.com/en/docs/claude-code/hooks instead of pane guessing: sessions launch with a generated --settings file whose hooks write the lifecycle state working , waiting , finished , idle to a per-session status file that the poller reads first. Pane rules still refine it — hooks cannot see a plain-text question, an Esc interrupt, or an error line, so a matching pane verdict upgrades the hook status — and they take over fully as fallback when the hook file is missing or stale. Enabled per tool with status source = "claude-hooks" . The header shows a fleet summary: per-status session counts, plus agents total usage: cpu N% · ram M% · X GB for every live agent's full process tree shell, agent, and children . CPU is that tree's CPU time over the last poll as a share of total machine capacity same 0–100% unit as the computer gauge . RAM is resident set as a share of installed memory, with absolute size beside it. The selected session's detail line uses the same scale for that session alone. The Computer block in the sessions panel shows machine gauges: CPU : whole-machine utilization 0-100% Memory : used/total. On macOS this matches Activity Monitor's Memory Used resident RAM minus free, speculative, and reclaimable file cache . On Linux it is Total - MemAvailable , so file cache is not counted as used. Swap : used/total of the current swap allocation used/total 100 . On macOS the swap file grows under pressure, so the denominator is the live size from vm.swapusage , not a fixed partition. Disk : fill of the root filesystem used / used + available , with free space from the kernel's available figure Network : up/down rates on real NICs only loopback, utun, bridges, and similar virtual interfaces are excluded s opens Settings, where ↑↓ move between fields and ←→ change the focused one. Nine palettes ship: classic , solarized dark , catppuccin mocha , tokyo night , gruvbox dark , nord , dracula , rosé pine , and monochrome . The swatch strip beside the name previews the palette, and the theme applies as you step through it, so the picker is a live preview of the whole UI. The manager also matches the terminal's own background to the palette, so the window has no seam against it, and restores the terminal's background on exit. Your pick is saved with the rest of the state and restored on the next run. Config lives in your OS user config dir ~/Library/Application Support/agent-manager/config.toml on macOS, ~/.config/agent-manager/config.toml on Linux and is created on first run with working defaults for Claude Code, OpenCode, Codex, and Grok Build. Top-level: poll interval default "2s" sets how often panes are polled for status, preview, and stats. Add any CLI tool as a tools.<name block: tools.mytool command = "mytool" default status = "idle" rules = { state = "working", pattern = "esc to interrupt" }, { state = "errored", pattern = " ?im ^\\s error:" }, Rules match top-down against the visible pane text; first match wins, and default status applies when nothing matches. Optional per-tool fields refine detection: activity cutoff regex locating the tool's input box, everything above it is turn content , turn end a turn-summary line marking the turn as over , chrome line , blocked line , and trailing note . The generated config's claude and opencode blocks show all of them in use. Other per-tool fields: revive command is what v runs to revive a dead session e.g. claude --continue resumes the conversation in place ; status source = "claude-hooks" switches status to Claude Code hook events see Status status . prompt flag controls how the new-session form's optional prompt is embedded into the launch command. Tools that take the prompt as a positional argument Claude Code: claude 'the prompt' leave it empty; tools whose positional argument means something else declare the flag OpenCode: prompt flag = "--prompt" , since its positional argument is the project path . The prompt only shapes the launch command; revive v uses revive command untouched. State is stored next to the config in state.db SQLite . go test ./... includes end-to-end tests against a real tmux server go run .