Documentation • Using atc • Configuration

atc lets you run several coding agents at once in a single terminal pane and keep track of which are waiting on you.

claude, grok, and codex sessions all run in a background daemon, with a session list in front of them. There are no panes. One session fills the terminal, Ctrl-Space opens the list, a session that needs an answer turns red, and Tab takes you to it. Quit atc and the sessions keep running.

Install

brew install zgeoff/tap/atc

atc needs at least one of the claude, grok, or codex CLIs on your PATH. The install guide covers the install script and the prebuilt binaries for macOS and Linux. atc ships only as binaries; the npm package is deprecated.

Then run atc. The first run starts the daemon. Press n to spawn a session, Ctrl-Space to see the rest, and ? for every other key.

Supported agents

• Claude Code reports its state on its own, through a settings file atc passes at spawn, and takes messages from other tools.
• Grok Build and Codex CLI take a one-time hook install that atc prints for you (Grok and Codex hooks).
• A Claude-compatible backend runs as its own agent in the same fleet (gateways).

Features

• Attention routing. Sessions that need you sort to the top, and a Claude session's statusline shows who's waiting (using atc).
• Sessions outlive the daemon. A restart, or an upgrade with u, brings every session back from its transcript (restarting).
• Agents that drive agents. atc mcp hands any agent the fleet as MCP tools, so it can spawn, read, and message other sessions (agents that drive agents).
• Hosted assistants. atc mcp --http serves the same tools to ChatGPT or Claude.ai behind OAuth, with the scopes you approve (remote MCP).
• Several machines. atc-gateway serves the fleets of several daemons through one connector (gateway).
• Session sandboxing. A session can run in its own VM, sleeping when you kill it and waking where it left off (targets).
• Event stream. atc events prints every fleet event, and config.json hooks run your own commands on them (events).

Configuration

atc creates ~/.config/atc/config.json on first run. The configuration guide covers every field: the agents and their arguments, the leader key, targets, gateways, principals, and hooks.

Documentation

docs/ covers how atc works, the guides, and the runbooks.