CLI — agentop
agentop is a single binary. The full reference is always one command away:
agentop --helpagentop --versionThe cockpit
Section titled “The cockpit”agentop # opens the cockpit (same as agentop start)agentop start --lang pt # force Portuguese for this runagentop tui # alias for agentop startTabs, in order: Services, Sessions, Backup, the metrics tab, Hardware, Logs,
Cheat sheet, Help and Contribute. The metrics tab needs no browser and has the
Overview, Projects, History, Costs, Harnesses and Hardware screens, switched with 1 to 6; f
filters by harness.
| Key | Does |
|---|---|
← / → |
change tab |
tab |
change pane |
enter |
actions for the selected row |
q |
quit |
Without an interactive terminal (a pipe, a systemd unit), agentop behaves like
agentop server.
Local server
Section titled “Local server”agentop server # web on :47292, API and MCP on :47291agentop server --port 4000 # API on 4000, web on 4001agentop server --bg # in the background, logging to ~/.agentisticsagentop status # services and health, without opening anythingagentop restart # restarts the service installed by autostartagentop watch # only the OpenTelemetry metrics daemonSessions
Section titled “Sessions”Background sessions run in tmux, on their own socket (-L agentop): they survive agentop
exiting and never mix with your own tmux sessions.
agentop session <harness> [-p "prompt"] [--bg] [--model <id>] [--effort <level>] [--cwd <path>] [--name "label"] [--task "<name>"]agentop session ls [--all] [--group <dimension>] [--json]agentop session attach <id|name>agentop session kill <id|name>agentop session rename <id|name> "label"agentop session note <id|name> "text"lsshows only what is running, grouped by project.--alladds finished, lost and closed sessions.--grouptakesproject,tree,repo,task,harness,model,status,markedandnone.- Without
--bg, the session takes over your terminal; the key to detach is printed first. --effortapplies toclaude(low,medium,high,xhigh,max) andantigravity(low,medium,high).
Several sessions at once, all under the same task:
agentop session batch --task "landing page" \ --session "claude: write the hero" \ --session "codex: write the tests"agentop session open "landing page" # reopens the whole task laterTasks (Agentask)
Section titled “Tasks (Agentask)”agentop task # lists tasks with their summed costagentop task show <id|name> # one task, its attempts side by sideagentop task deliver <ref> # marks it done and attaches the git evidenceagentop task abandon <ref> # marks it abandonedAll of them accept --json.
Claude Code in parallel
Section titled “Claude Code in parallel”agentop hooks install # installs a skill and a SessionStart hook into Claude Codeagentop hooks statusagentop hooks uninstall # removes exactly what install wroteThe skill teaches Claude Code to propose splitting work across several sessions with
agentop session batch; the hook tells it which sessions are already running. Nothing is written
to ~/.claude before you run install, and Claude always asks for your yes before starting
sessions.
Session alerts
Section titled “Session alerts”agentop events watch --desktop # notifies when a session waits, asks for permission or exitsagentop events statusBackup
Section titled “Backup”agentop backup # metrics plus a manifest that rebuilds your repositoriesagentop backup --plan # shows what would be written, writes nothingagentop backup schedule dailyagentop restore <archive>Credentials are never included in a backup.
Updates and autostart
Section titled “Updates and autostart”agentop upgrade # updates to the latest versionagentop check-update # speaks up only when there is a new versionagentop autostart server enable # starts the server with the systemagentop autostart statusagentop autostart server disable