Your own sign-ins, as members of a thread.
CommandAGI runs the coding CLIs you already pay for on your computer, signed in as you. Each one is an agent with its own principal, its own sign-in and its own stream.

One turn
The CLI runs as itself.
The host starts the CLI in the member's worktree, on the member's sign-in, with CommandAGI's MCP server for that run only. It reads the CLI's own output stream back as records.
Case study · the backlog thread
6,641 turns on seven sign-ins.
CommandAGI's own backlog thread, 2026-10-23 to 2026-11-04. Claude Code ran on five sign-ins and Codex on two. A CLI can also run another model through its route: most of Claude Code's turns here ran DeepSeek through an Anthropic-compatible endpoint.
Gemini CLI and Cursor. Both are harnesses with launch plans and parsers, held by the host's tests. Neither took a turn in this thread, so this page has no numbers for them yet.
- Claude Code turns
- 5,619
- Codex turns
- 1,022
- tool calls, each a record
- 469,557
- of 2,155 usage-policy checks allowed the turn
- 2,153
runs/20261023t132208z-0aea (the backlog thread, on this computer)Output case-studies/backlog-thread/stats.jsonTool scripts/sites/case-studies.mjs backlog-threadRan on This computer (dell-gb10-1), reading the run folderWhen One turn, as the CLI reported it.
Member a1's first turn of Claude Code. The sign-in, the tool's input and each line's hlc and salt are left out.
13:22:31.800 event policy cli=claude allowed weekly 27% under its cap of 80% (claude-*) 13:22:31.863 command agent:task-loop@dell-gb10-1: prompt agent=a1@dell-gb10-1 cli=claude model=claude-opus-5-5 13:22:34.740 event session model=claude-opus-5-5 13:22:37.363 event tool Bash 13:22:37.364 event limit allowed five_hour 0% seven_day 26% 13:22:37.395 event tool-result ok
Bring the plans you already pay for.
Install a CLI, sign in once, and add it to a thread.