Home Switch T3 Code

Switch from T3 Code to Task Machine

T3 Code puts coding-agent threads on computers you manage. Task Machine gives people and agents shared Tasks with plans, review and an Inbox for decisions.

Prefer the side-by-side comparison?

Why people switch

  • Keep a computer available

    T3 Code's phone app is a remote. The computer doing the work needs to stay on.

    github.com/…/faq.md
  • Review the starting permissions

    T3 Code's initial default for new threads is Full access, which allows commands and edits without approval prompts. You can change that default or use an administrator cap.

    github.com/…/permission-modes.md
  • Carry context deliberately

    T3 Code's portable handoffs transfer selected conversation history when changing providers or restarting. They exclude the outgoing provider's reasoning, tool-call state and attachments.

    github.com/…/portable-handoffs.md

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.

What each part of T3 Code maps to in Task Machine, with the source and check date of each answer
Area In T3 Code In Task Machine
Work records In T3 Code

Use a thread for a separate task. A new worktree gives its code changes a separate branch and working directory.

github.com/…/thread-sidebar.md
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 hand work to each other on the same record.

taskmachine.io/docs/tasks
Recurring work In T3 Code

Scheduled tasks run once or repeatedly on a chosen environment. Webhook tasks start from service events, and runs can start new threads or reuse a thread.

github.com/…/project-settings.md
In Task Machine

Start a Task or Workflow on a schedule in your timezone or from a service event. A recurring job keeps one stable root Task, with each occurrence's own status and history.

Approval In T3 Code

Permission modes apply to a thread. Approve or reject requests in its conversation, including requests from delegated subagents.

github.com/…/permission-modes.md
In Task Machine

Decisions land in your Inbox with their context. Set each agent's actions to Ask first or Automatic, and put a Human approval step before publishing a report or changing a record.

Execution In T3 Code

Agents run on your desktop, server or virtual private server. Desktop, web and phone clients show the same threads.

In Task Machine

Run agents in Managed Cloud with nothing to install, or connect a Local Worker for files, tools and accounts on a computer you control. You choose where each agent runs.

Model accounts In T3 Code

T3 Code drives coding agents you are already signed in to. You can change models during a thread, and it does not resell tokens.

github.com/…/README.md
In Task Machine

Auto chooses a model for each stage from the task, model capabilities, pricing and budgets. You can fix a model on an agent or sign in to connected subscriptions on a Local Worker.

Code review In T3 Code

Pull-request watches wake an agent when checks fail, required checks pass, review feedback arrives or the branch conflicts. You can stop a watch from the thread.

github.com/…/source-control.md
In Task Machine

Internal review checks changes against enabled repository rules. Merge risk rates the exact revision Low, Moderate or High with evidence for your final decision, and never merges for you.

Pricing In T3 Code

T3 Code is free, MIT-licensed software. You pay your provider separately, and T3 Connect is currently free for up to three linked machines.

github.com/…/faq.md
In Task Machine

Usage based, from $29 a month before tax. The whole payment becomes usage that your workspace shares, with no base fee.

taskmachine.io/pricing

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. T3 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 T3 Code if

You may stay with T3 Code if hands-on coding is your main job and you already have the computers and agent subscriptions you need. Its desktop, web and phone clients let you follow the same threads, switch models and review code changes. Its free MIT-licensed software is a reason to keep it for that work while moving only selected recurring jobs.

What you give up

Task Machine's docs do not describe a T3 Code thread importer or a way to control your installed coding agents as T3 Code does. A Local Worker uses tamacode, Task Machine's own coding agent, with separately connected model subscriptions. You must reconnect accounts, rewrite prompts as Tasks or Workflow steps and test the replacement's permissions.

There is no trial. Work consumes usage, including ordinary unsuccessful attempts, so budget for the migration checks as well as the first live job.

How the switch works

  1. Preserve repository branches, uncommitted files, important attachments and the instructions from the threads you are moving. Check T3 Code's export options before removing anything. Its portable handoffs describe context transfer between its providers, not a transfer into Task Machine.
  2. Create a workspace and choose Managed Cloud or a Local Worker. Connect the repository and service accounts the selected job needs. Keep repository instructions in TAMA.md as the repository guide explains.
  3. Create one Task with a named owner, expected result and acceptance criteria. For a recurring job, rebuild the saved prompt in a Workflow, with separate steps for drafting, checking and approval. Save reference material in the Library.
  4. Set autonomy to Ask first for unfamiliar actions. Test with copied inputs and review the output and Run history before allowing live writes or sends.
  5. Pause the old job in T3 Code's Scheduled tasks settings and stop any pull-request watch you are replacing. Redirect event senders to the new Connector, then enable the replacement's schedule. Keep the old records until you have checked the first live result.

Common questions

Do I have to stop using T3 Code?
Move one job first. Keep T3 Code for the coding threads you still want to supervise directly, and give Task Machine the work you want tracked as shared Tasks.

Can I import my threads and files?
Task Machine's docs do not describe a T3 Code thread importer. Check your export options, retain the original records and upload selected reference files to the Library. T3 Code's handoff documentation says its internal handoffs exclude attachments, so preserve those separately.

How do the costs compare?
T3 Code is free software with separate provider costs. Task Machine's pricing funds usage for AI work and execution from $29 a month before tax, with no base fee and no trial. Compare one representative job because the payments cover different things. You keep 100% of your revenue, Task Machine takes no cut, and never custodies your accounts.

Can I keep my model subscription?
T3 Code lets you use an existing Claude Code subscription. Task Machine has its own Local Worker sign-in for supported subscriptions. Connect it separately rather than assuming a T3 Code login or coding-agent installation transfers.