Skip to main content
Cyclops is a coordination layer for coding agents running in tmux. tmux continues to own the panes, processes, scrollback, and detach behavior; Cyclops observes and coordinates them.

​
What it adds

  • Stable names for agent panes, such as implementer and reviewer.
  • Agent state derived from vendor hooks, pane titles, output, and screen evidence.
  • Durable workspace mailboxes with authenticated senders and exact claims.
  • One doorbell line per message with a separate wake state: a one-line preview and the exact claim command, while the full body remains in the authenticated mailbox.
  • A live stream and full-screen workspace for watching and controlling panes.
  • An append-only workspace message journal plus separate session state ledgers.
Cyclops ships twelve detection manifests. Five are measured against a live CLI: Claude Code, Codex CLI, Antigravity CLI, Cursor Agent CLI, and Kimi Code CLI. Seven are written from vendor documentation and marked unverified: Gemini CLI, Qwen Code, goose, OpenCode, Amp, Crush, and aider. Another terminal CLI needs a manifest, not a Cyclops SDK or wrapper. Support is version-specific. A manifest measured against one version may misread the next; the doorbell still goes through, and a line that could not be read back is recorded as unverified rather than retried. An unverified manifest carries no composer rule, so it never detects a human draft. The Cursor terminal path has fixture coverage but no live current-version run, because no current Cursor binary was available on the evidence host. See Recover a notification.

​
The two processes

cyclopsd is the daemon. It holds one tmux control-mode connection per watched session, fuses state, owns durable mailboxes, and writes the journals. cyclops is the user-facing command. A bare cyclops opens the full-screen workspace. Subcommands such as cyclops status, cyclops send, and cyclops watch talk to the daemon over a Unix socket.

​
Talking to your agents

Day to day, you don’t type cyclops subcommands at your agents. You talk to them the way you’d talk to a teammate: “send this to reviewer and ask for a review.” An agent that knows the verbs turns that into a handoff through the cyclops CLI itself, and the workspace shows the receipt. That “knows the verbs” part comes with the install. The agent skill at skills/cyclops/SKILL.md teaches the cyclops verbs. Setup places it at ~/.claude/skills/cyclops/SKILL.md for Claude Code, one shared ~/.agents/skills/cyclops/SKILL.md for Codex and Cursor, and ~/.gemini/antigravity-cli/skills/cyclops/SKILL.md for Antigravity CLI when those consumers are installed and have already created a private canonical skill parent. Setup never creates a consumer skill directory, and a copy you edited is never overwritten.

​
Next steps