Docs · Configuration

Any CLI, in five lines of TOML.

Config lives in your OS user config directory, at ~/.config/agent-manager/config.toml on Linux or ~/Library/Application Support/agent-manager/config.toml on macOS, and is written on the first run with working defaults for Claude Code, OpenCode, Codex and Grok Build. poll_interval (default "2s") sets how often panes are polled for status, preview and stats.

Adding a CLI

Any other CLI runs as a session immediately, and earns live status the moment you describe it:

[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 and the first match wins; default_status applies when nothing matches.

Refining the status

activity_cutoffRegex locating the tool's input box. Everything above it is turn content.
turn_endA turn-summary line marking the turn as over.
busy_lineWork that outlives its turn, such as background agents.
chrome_lineInterface furniture to ignore when reading the pane.
blocked_lineA line that means the agent is waiting on you.
trailing_noteTrailing output that should not count as activity.
status_source"claude-hooks" takes the status from Claude Code hook events instead of the pane. See Status.

The generated config's claude and opencode blocks show all of them in use.

Revive and prompts

resume_by_id_commandResumes one exact conversation, with {id} replaced by the session's captured agent id.
session_id_flagLaunches the tool under an id the manager mints, for example --session-id.
session_store"codex" or "opencode", to read back an id the tool minted itself.
revive_commandWhat v falls back to when no id is available, such as claude --continue.
prompt_flagHow the form's optional prompt enters the launch command. Empty for tools that take it positionally (claude 'the prompt'); OpenCode declares --prompt, since its positional argument is the project path.
mcp"claude" | "codex" | "opencode" | "grok" | "gemini" | "none", picking how the MCP server is registered. See MCP tools.

Themes

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 the picker, so it 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 it on exit.

The settings screen with the theme picker and a strip of palette swatches beside the theme name.

State

Order, groups, archive, theme and the split ratio live in state.db, a SQLite file next to the config, and are restored on the next run.