Switch from Claude Code to Task Machine
Claude Code's cloud scheduled tasks belong to individual accounts. Task Machine puts recurring work in a shared workspace with Tasks, review gates and Inbox decisions.
Prefer the side-by-side comparison?Why people switch
-
Schedules need shared ownership
Claude Code's research-preview cloud scheduled tasks belong to your individual account and are not shared with teammates. Their actions use your connected identities.
-
Cloud rules differ
In public-beta Projects, cloud threads do not read permission rules from a repository's .claude/settings.json. You rely on auto mode and approvals given inside each thread.
-
Success needs another check
A scheduled run marked Succeeded means the session ended without a reported failure. Anthropic says this does not establish that Claude completed the work in your prompt.
What maps to what
Every answer links to its source and shows when we last checked it. The oldest check on this page was November 15, 2026.
| Area | In Claude Code | In Task Machine |
|---|---|---|
| Projects |
In Claude Code
Projects coordinate parallel threads with shared instructions and memory. They are a gradual public beta on Pro, Max and Ultra, not yet offered on Team or Enterprise. |
In Task Machine
Every job is a Task that a person or an agent owns. Its plan, discussion, decisions, runs and history stay together, so people and agents can hand work to each other on the same record. |
| Recurring work |
In Claude Code
Research-preview cloud scheduled tasks start on a schedule, an API call or a GitHub event. Each configuration combines a prompt, repositories and connectors. |
In Task Machine
Start a Task or Workflow once or on a repeat in your timezone. A recurring job keeps one stable root Task, with each occurrence's own status and history. |
| Approval |
In Claude Code
Public-beta Projects show threads needing a reply or approval under Waiting on you. The actual approval prompt must be answered inside its thread. |
In Task Machine
Decisions land in your Inbox with their context. Set each agent's actions to Ask first or Automatic, such as asking before sending a message to a customer. |
| Memory |
In Claude Code
Local auto memory keeps corrections and preferences in editable files. Public-beta Projects have separate memory files that later cloud threads read. |
In Task Machine
Agents keep lessons such as an accepted example or a mistake to avoid. Notes belong to an agent, project, goal, team or workspace, and you can read, correct and restore them. |
| Connections |
In Claude Code
Model Context Protocol servers give Claude Code access to tools, databases and APIs, such as reading an issue tracker or creating a Gmail draft. |
In Task Machine
Install services from the Connectors catalog or add a custom connection through an API, a command-line tool or Model Context Protocol. Assign each connection to the agents that need it. |
| Execution |
In Claude Code
Claude Code works in your terminal, editor, desktop app and browser. Cloud sessions can continue when your computer is off. |
In Task Machine
Run agents in Managed Cloud with nothing to install, or connect a Local Worker, a computer you control, for local files, tools and accounts. You choose where each agent runs. |
| Pricing |
In Claude Code
Claude Pro includes Claude Code for $20 billed monthly, excluding applicable tax. Subscriptions have usage limits shared across Claude surfaces. Console access instead bills per token. |
In Task Machine
Usage based, from $29 a month before tax. The whole payment becomes usage that your workspace shares, with no base fee. |
A fact we cannot find or cannot check is left out, and prices can change after the date shown. Task Machine publishes this comparison and is an interested party. Claude Code is named only to identify it, and there is no relationship between the two companies. Has something changed? Tell us.
You may stay with Claude Code if
You may stay with Claude Code if you mainly want to write and review code inside your editor. Its editor integrations include inline diffs, plan review and conversation history. Its public-beta Projects also coordinate ongoing work and handle uploaded documents, so needing work beyond a terminal session alone is not a reason to move.
What you give up
Task Machine's docs do not describe an equivalent editor extension or an importer for Claude Code sessions. Task Machine does not host Claude Code as a worker. You rebuild the selected job with Task Machine agents and review its instructions, connections and approval boundaries rather than moving the harness unchanged.
There is no trial. Your first payment funds usage, and unsuccessful attempts can still consume it. Reconnecting services, checking saved guidance and testing a representative run take time. Read Billing before moving a recurring job.
How the switch works
- Keep your repository and unfinished changes. In the Claude Code CLI, export important conversations as plain text with
/export filename. Use /memory to locate and copy local instructions and memory files. If you use Projects, copy the separate instructions and notes from Project settings. Record each scheduled job's prompt, triggers and connected services from its detail page. - Create your workspace, connect the repository and add the required Connectors. Upload useful exports to the Library as reference files. Review repository guidance and put the instructions for Task Machine runs in
TAMA.md. - Choose one job, such as a weekly dependency audit. Create a Task with an agent owner and a result you can check, or rebuild a multi-step process in the Workflow builder. Curate reusable lessons into Memory.
- Start with Supervised autonomy. Review the plan and completion requirements, then test with copied inputs and explicit approval before external writes. Check the result and evidence in Task reviews.
- Confirm the schedule and timezone. Pause the original Claude Code schedule and remove or redirect its event triggers before enabling replacement writes, so both processes do not act on the same input.
Common questions
Does Task Machine run Claude Code for me?
No. Task Machine uses its own agents. A Local Worker is a computer you control, not a hosted Claude Code session.
What happens to my conversations and memory?
Keep plain-text conversation exports, your source files and copies of the memory notes you need. Store useful references in the Library and review lasting lessons before adding them to Memory. Task Machine's docs do not describe importing Claude Code session state.
How do the costs compare?
Claude Code shares a subscription's usage limits with other Claude surfaces, while Console usage bills per token. Task Machine's pricing funds workspace usage from $29 a month before tax, with no base fee and no trial. Compare the same job's actual usage rather than treating either payment as a fixed number of completed jobs. You keep 100% of your revenue, Task Machine takes no cut, and never custodies your accounts.
Must I move all coding work?
Move one recurring responsibility first. Keep Claude Code's editor workflow where it already fits, and use Task Machine for shared Tasks and decisions you want to review in Inbox.