All comparisons
OpenCharts · Always-on workers
Theo Claw vs Codex
OpenAI's software engineering agent: a cloud sandbox per task, plus a CLI and an IDE extension
Codex is the best kind of narrow: give it a repository and a task and it works until there is a pull request to read. Theo Claw Code does the same job as one mode of a colleague that also watches an inbox, answers the phone, runs every morning, and asks you a question when it genuinely needs one.
By OpenCharts TeamPublished
Theo Claw is OpenCharts' always-on autonomous worker and its code mode is directly comparable to Codex: both clone a real repository into a cloud workspace, read and edit files, run commands and tests, and open a pull request you review. They diverge on scope and governance. The same Theo Claw worker can also hold a phone number, email address and calendar, listen in Slack, run named jobs on a schedule, pause to ask a plain question mid-task, earn autonomy one kind of action at a time, write a receipt for every run, and publish a finished run as a read-only page. Codex leads on terminal and editor integration, parallel coding tasks, and review tooling built around diffs.
Theo Claw vs Codex✳The verdict✳When to choose✳Feature matrix✳Pricing snapshot✳Migration✳FAQ✳Theo Claw vs Codex✳The verdict✳When to choose✳Feature matrix✳Pricing snapshot✳Migration✳FAQ✳
The verdict
Where each one wins
Theo Claw wins at
- The same worker also answers email, texts, calls and Slack, so shipping the fix and telling the customer are one job
- A choice of engines from several labs per worker, with cost tiers, or your own provider key
- A structured question mid-task, with one-tap options, instead of guessing or stopping
- Autonomy earned one kind of action at a time, with deleting never earnable
- Receipts for every run: the engine, pages, messages, teammates and credits
- A public read-only page for a finished run, with no repository access required
- Several named standing jobs per worker, each on its own schedule
- Work outside code lands as editable decks, documents, sheets and apps
Codex still wins at
- Terminal and editor integration built around an engineer's working day
- Starting many independent coding tasks and reviewing the results side by side
- Review workflows centered on diffs and existing pull requests
How they compare
Theo Claw and Codex solve overlapping problems differently. The matrix below makes the trade-offs concrete, and the migration note covers what it takes to switch when you're ready.
When to choose
The right pick for your team
Choose Theo Claw when…
- The job does not stop at the pull request: someone has to be emailed, called, or updated in Slack.
- You want one worker that ships code on Tuesday and clears an inbox every morning.
- Your team needs approvals, receipts, a trust ladder and org rules before an agent acts.
- You want to choose, or let Theo choose, which engine does the thinking and see what the run cost.
- You want to show somebody what the worker did without giving them repository access.
Choose Codex when…
- Your work is entirely code and your team lives in the terminal and editor.
- You want to start many independent coding tasks and review the diffs together.
- You want an agent that reviews existing pull requests as its main job.
Side by side
Feature comparison
Feature
Theo Claw
Codex
Working in a real repository
A persistent workspace per worker with the repository cloned, a terminal, browser and files; it branches, commits, pushes and opens a pull request under your connected account
A cloud sandbox per task with the repository preloaded; it runs commands and tests and opens a pull request
Which model does the work
A Brain policy per worker: let Theo orchestrate across engines from several labs, pick economy, pin one engine, route writing, reasoning, vision and code separately, or use your own provider key
A choice between the vendor's own coding models
What else the worker does
The same worker can hold a phone number, email address and calendar, listen in Slack, answer Telegram and a REST API, and produce decks, documents, sheets and apps
Software engineering tasks
Asking you something mid-task
It pauses with a plain question and up to four one-tap options, or takes your own words; answering is not an approval and authorizes nothing
Clarification happens in the task thread
Approvals
Full autonomy, ask before risky, or ask before everything; one approval covers a multi-step plan with reversibility marked, and org rules override any worker
Sandbox network access and approval modes configured per environment
Earning autonomy
Opt a kind of action in and consecutive approvals earn it; one rejection resets the streak and deleting is never earnable
Approval mode is a setting, not something the agent earns
Audit trail
A receipt names the engine, web pages and company knowledge read, messages sent, teammates used and credits spent
Task logs, the diff and terminal output
Showing somebody the work
Publish a frozen read-only run page with the plan, steps and artifact names; recipients, private files and company knowledge are never included
Share the pull request, which requires repository access
Standing work
Several named routines per worker, each on its own schedule, plus missions that wait for a time or page change and resume across days
Scheduled tasks start fresh runs
Spend control
A per-turn credit gate warns early and pauses when the next step cannot be covered; a top-up resumes where it stopped
Subscription rate limits with paid credits on top
Seeing what is running
Presence per worker, one queue of everything blocked on you, and a catch-up line when you return
A task list with each task's state
Testing a configuration change
Replay past runs against a new engine, persona or tool set and diff the decisions; nothing is executed
Not offered
Scroll to compare
Pricing and migration
What it costs, what it takes
Pricing
Pricing snapshot
Theo Claw is included from OpenCharts Starter at $9.99/mo, with Pro at $24.99/mo and Teams at $14.99 per user per month; runs spend the same AI credits every other Theo surface uses, and a dedicated SMS number is a monthly add-on. Codex is included with the vendor's paid consumer and business plans, with rate limits per plan and paid credits on top. List pricing at time of writing (September 2026).
Migration
Migrating from Codex
There is no import between the two, and none is needed because both work from the same repository. Create a Theo Claw worker from the Software engineer starter, connect the same code host, choose the repositories it may touch, and paste the task instructions as its goal. Add anything that should happen after the pull request, such as telling a customer or updating a sheet.
Questions
Frequently asked questions
Does Theo Claw work in my repository, or only scaffold code?
It works in the repository. A code worker gets a persistent workspace with the repository cloned, a terminal and a browser. It reads and edits files, runs your commands and tests, commits to a branch, pushes and opens a pull request under your connected account. Pushing to the default branch and merging are risky actions, and force-push stays off unless you allow it.
What does Theo Claw do that a coding agent does not?
The same worker is useful outside the repository. It can hold a phone number for texts and calls, its own email address and calendar, listen in Slack, run several jobs on a schedule, and produce decks, documents and sheets. A fix that must be shipped and then explained to a customer is one worker rather than two tools and a copy-paste.
Can a worker ask me a question instead of guessing?
Yes. It can stop mid-task and ask a plain question with up to four buttons or take an answer in your own words, then continue from exactly where it paused. Answering a question is not an approval and authorizes nothing, which is why the two controls look different.
Can I show somebody a run without giving them access?
Yes. Publish a finished run and anyone with the link can read its plan, steps and artifact names with no account. It is a frozen snapshot, so it cannot widen later. Message recipients, private files and company knowledge are never included, and removing the link deletes it.
Which one should a small engineering team pick?
If the work is entirely code and the team lives in the terminal and editor, a dedicated coding agent is closer to hand. If the work spills into inboxes, customers, schedules and documents, and you want approvals, receipts and per-run cost, Theo Claw covers the whole job.
Hire a worker that keeps working
Give a Theo Claw worker a goal, the tools it may use, and how much rope it gets. It runs while you sleep and asks before anything risky. Included from the Starter plan, with the whole workspace alongside it.
Included from Starter · Approvals and receipts on every run