
Theo Agent vs Claude Code
Anthropic's terminal coding agent: repository-aware, extensible through skills, hooks, subagents and MCP
Claude Code is a coding harness an engineer shapes around a repository with instructions, skills, hooks and subagents. Theo Agent is the colleague that keeps that repository context and then leaves the terminal: it wakes on a schedule, answers people, and reports what it did when nobody was watching.
Theo Agent and Claude Code can both read a repository's own instructions, work in a real clone, edit files, run commands and tests, and open a pull request. Claude Code is the stronger coding harness for a developer who is present: its terminal workflow, repository instruction files, skills, hooks, subagents and MCP ecosystem make it deeply programmable. Theo Agent is built for the work nobody is watching. The same worker can answer email, Slack, texts and calls, run several named jobs on schedules, wait for a page to change, ask a structured question mid-run, earn autonomy one kind at a time, write a receipt for every run, surface every blocked worker in one queue, and publish a finished run as a safe read-only page.
Where each one wins
- Always-on work started by schedules, inbound messages, calls, page changes and long-lived missions
- Reach outside a terminal: a phone number, email address, calendar, Slack, Telegram and a REST API
- A choice of engines from several labs per worker, with per-job routing, or your own provider key
- Autonomy earned one kind of action at a time, plus org-wide approval rules
- Receipts that name sources, messages, teammates, credits and earned-trust actions
- A cross-worker needs-you queue and a catch-up line when you return
- Editable decks, documents, sheets, apps and media in the same workspace
- A safe public snapshot of a finished run

- A mature terminal-first coding harness that stays close to the repository and developer
- Repository customization through instruction files, skills, hooks, commands, subagents and MCP
- Interactive code review and debugging while an engineer is present
Use Claude Code when you are at the terminal and Theo Agent for the repository work that should happen while nobody is there. Theo Agent also reads AGENTS.md, CLAUDE.md or Theo.md when it opens a repository, so the same project guidance can govern both.
The right pick for your team
Choose Theo Agent when…
- The task should start from an inbox, schedule, phone call or page change rather than from your terminal.
- The worker must continue into customer communication, calendars, sheets or presentations after the code lands.
- Your team needs one place to see every worker that is blocked and what it needs.
- You want earned autonomy, org rules, receipts and a public run snapshot.

Choose Claude Code when…
- You are at the keyboard and want the deepest terminal-first coding loop.
- Your repository already has a large investment in custom skills, hooks and subagents.
- You want to inspect, steer and debug the coding loop turn by turn.
Feature comparison

What it costs, what it takes
Pricing snapshot
Migrating from Claude Code
Frequently asked questions
Is Theo Agent a replacement for Claude Code?
Does Theo Agent read CLAUDE.md or AGENTS.md?
Can Theo Agent use my installed skills?
Which one is better when I am not at my computer?
Can I use both on the same repository?

Hire a worker that keeps working
Give a Theo Agent worker a goal, the tools it may use, and an approval policy. It works within those boundaries and reports back. Included from the Starter plan, with the whole workspace alongside it.
Included from Starter · Approvals and receipts on every run