# Traycer vs T3 Code: two open-source agent apps, compared honestly

By Tanveer Gill | Published 2026-10-25

Source: https://traycer.ai/compare/traycer-vs-t3-code

> T3 Code vs Traycer: two free, open source (MIT) apps for Claude Code, Codex and Cursor, compared on shared plans, PRs, mobile, automation and team sharing.

*By Tanveer Gill. Last checked: October 24, 2026.*

T3 Code and Traycer are both free, open source (MIT) apps that run Claude Code, Codex, Cursor and other coding agents with the subscriptions you already have. Both isolate work in git worktrees, ship phone apps and let one agent hand work to another. T3 Code is the stronger pick if you want a fast, lightweight control plane with a web app, scheduled and webhook-triggered tasks, inline diff comments and stacked pull requests. Traycer is the stronger pick if you want agents to work from one Task's shared specs and tickets, message each other across Tasks and machines, and share that work with teammates.

*Both projects ship several times a week. T3 Code (t3code on GitHub) publishes nightly builds, so check the linked docs before you decide.*

## TL;DR

**Pick T3 Code if you:**

- Want agents to run on a schedule or when a webhook fires, such as a new pull request ([project settings](https://github.com/pingdotgg/t3code/blob/main/docs/user/project-settings.md)).
- Live in the pull-request loop: one button to commit, push and open a PR, plus draft and stacked PRs across several git hosts ([t3.codes](https://t3.codes/), [source control](https://github.com/pingdotgg/t3code/blob/main/docs/user/source-control.md)).
- Want to fork and reshape the whole app, which its README names as a goal.

**Pick Traycer if you:**

- Want to work from anywhere: desktop apps for macOS, Windows and Linux, plus iOS and Android apps on the Free plan that reach your machines through Traycer's relay ([mobile app](https://docs.traycer.ai/account/mobile-app)).
- Want parallel agents to work from the same specs, tickets and reviews instead of separate chat histories ([artifact workflow](https://docs.traycer.ai/concepts/artifact-workflow)).
- Plan before you build: brief, core flows, tech plan, tickets, then batched execution reviewed against the plan.
- Want agents to message each other across Tasks and across your machines ([agent-to-agent](https://docs.traycer.ai/concepts/agent-to-agent)).
- Need teammates to see, comment on and steer agent work ([sharing](https://docs.traycer.ai/panels/sharing)).

**Use both if you:**

- Plan and coordinate a feature in one place but want to approve a run or check a PR from a browser in the other. Both work on plain git worktrees and the same agent CLIs.

## What each tool is

### What is T3 Code?

T3 Code calls itself "the open-source control plane for coding agents" on its site and an "agent harness control surface" in its README ([t3.codes](https://t3.codes/), [repo](https://github.com/pingdotgg/t3code)). It comes from Theo Browne and team; the repo lives under `pingdotgg`, was created on February 8, 2026, and is MIT-licensed. A local server runs your agents, and the Electron desktop app, the web app and the mobile apps connect to that server ([install](https://github.com/pingdotgg/t3code/blob/main/docs/user/install.md)).

It has eight built-in providers: Codex, Claude Code, Cursor, Grok Build, OpenCode, Antigravity, Pi and Muse Code (Muse is a beta and off by default). It can also run agents from the ACP Registry ([install](https://github.com/pingdotgg/t3code/blob/main/docs/user/install.md), [ACP providers](https://github.com/pingdotgg/t3code/blob/main/docs/user/providers-acp.md)). It's free. Under "Wait, what are you selling me?" the README answers: "Nothing." It's also candid about its stage: "We are very very early in this project. Expect bugs."

### What is Traycer?

Traycer is an open source (MIT) desktop app for macOS, Windows and Linux: a shared workspace for running coding agents in parallel ([docs](https://docs.traycer.ai/), [repo](https://github.com/traycerai/traycer)). Work is organized into Tasks. A Task holds its agents, files, terminals, the git diff and its artifacts: specs, tickets, stories and reviews that every agent in the Task reads and that outlast any one chat. It supports 22 coding agents, including Claude Code, Codex, Cursor and OpenCode ([coding agents](https://docs.traycer.ai/agents-and-models/coding-agents)). More than 11,000 developers have signed in to Traycer Desktop and created over 40,000 Tasks in it.

### The core difference

T3 Code's unit is the thread: one conversation with one provider in one checkout or worktree. Its center of gravity is the server that runs those threads and lets you reach them from any device. Traycer's unit is the Task: several agents plus the shared plan they all work from. Its center of gravity is that shared context. They suit different work.

## Side-by-side comparison

*Last checked: October 24, 2026. "Not documented" means we didn't find it in the linked docs on that date, not that it doesn't exist. Re-check before relying on any cell.*

| Criterion | T3 Code | Traycer |
| --- | --- | --- |
| What it is | "The open-source control plane for coding agents" ([t3.codes](https://t3.codes/)) | Open-source desktop app for running coding agents in parallel, with shared plans and code review ([docs](https://docs.traycer.ai/)) |
| Maker | Theo Browne and team; repo under `pingdotgg` ([repo](https://github.com/pingdotgg/t3code)) | Traycer ([repo](https://github.com/traycerai/traycer)) |
| License | MIT ([repo](https://github.com/pingdotgg/t3code)) | MIT ([repo](https://github.com/traycerai/traycer)) |
| Price | Free; no paid tier ([README](https://github.com/pingdotgg/t3code)) | Free, including cloud sync; Sync plan $20/user/mo or $16 billed yearly for team-wide sharing; optional pay-as-you-go credits ([pricing](https://docs.traycer.ai/account/pricing)) |
| Bring your own subscription | Yes: "doesn't resell tokens" ([t3.codes](https://t3.codes/)) | Yes: Claude Code, Codex, OpenCode and Cursor paths use no Traycer credits and no markup; Auto mode's judge is the exception ([pricing](https://docs.traycer.ai/account/pricing)) |
| Built-in agents | Codex, Claude Code, Cursor, Grok Build, OpenCode, Antigravity, Pi, Muse Code (beta) ([install](https://github.com/pingdotgg/t3code/blob/main/docs/user/install.md)) | 22 coding agents, including Claude Code, Codex, Cursor, OpenCode, Grok, Copilot, Kiro, Droid, Amp, Devin and Antigravity ([coding agents](https://docs.traycer.ai/agents-and-models/coding-agents)) |
| Other agents | Any ACP Registry agent, or a local ACP command ([ACP providers](https://github.com/pingdotgg/t3code/blob/main/docs/user/providers-acp.md)) | Chat or Terminal interface per agent, listed per agent ([coding agents](https://docs.traycer.ai/agents-and-models/coding-agents)) |
| Apps | Desktop (macOS, Windows, Linux), local and hosted web app, `t3` CLI, iOS and Android apps ([install](https://github.com/pingdotgg/t3code/blob/main/docs/user/install.md)) | Desktop (macOS, Windows x64, Linux x64), CLI, iOS and Android apps ([install](https://docs.traycer.ai/install), [mobile](https://docs.traycer.ai/account/mobile-app)) |
| Unit of work | Thread inside a project ([threads](https://github.com/pingdotgg/t3code/blob/main/docs/user/thread-sidebar.md)) | Task: several agents plus shared artifacts, files and diff ([artifact workflow](https://docs.traycer.ai/concepts/artifact-workflow)) |
| Worktree isolation | Current checkout or a new worktree per thread; worktree location setting; automatic cleanup rules ([threads](https://github.com/pingdotgg/t3code/blob/main/docs/user/thread-sidebar.md), [project settings](https://github.com/pingdotgg/t3code/blob/main/docs/user/project-settings.md)) | Local, New worktree or Existing worktree per folder; setup and teardown scripts; Sweep cleanup ([worktrees](https://docs.traycer.ai/concepts/worktrees)) |
| Agent-to-agent | `delegate_task` starts child agents on any provider; outside agents connect over MCP ([v0.1.0 notes](https://github.com/pingdotgg/t3code/releases/tag/v0.1.0), [outside agents](https://github.com/pingdotgg/t3code/blob/main/docs/user/outside-agents.md)) | Child agents; messages across Tasks and hosts; reading transcripts; agent roles ([agent-to-agent](https://docs.traycer.ai/concepts/agent-to-agent)) |
| Shared specs and tickets | `/plan`, skills and @-mentioning another thread; a shared spec and ticket layer is not documented ([composer](https://github.com/pingdotgg/t3code/blob/main/docs/user/composer.md)) | Artifacts (specs, tickets, stories, reviews) plus plan, execute and review skills ([artifact workflow](https://docs.traycer.ai/concepts/artifact-workflow)) |
| Switching providers mid-conversation | Supported, lossy by design: a budgeted selection of messages, 16,000 tokens by default, without reasoning or tool state ([portable handoffs](https://github.com/pingdotgg/t3code/blob/main/docs/user/portable-handoffs.md)) | Switch models within the same agent, with context shared across providers ([README](https://github.com/traycerai/traycer)); account switching and optional routing when blocked ([usage and routing](https://docs.traycer.ai/agents-and-models/usage-limits-and-routing)) |
| Permission modes | Supervised, Auto-accept edits, Auto, Full access; Full access is the initial default ([permission modes](https://github.com/pingdotgg/t3code/blob/main/docs/user/permission-modes.md)) | Supervised, Auto-accept edits, Auto (experimental), Full access; Full access is the default ([permissions](https://docs.traycer.ai/settings/permissions)) |
| Diff review | Review comments from a diff go back to the agent; revert to an earlier message ([composer](https://github.com/pingdotgg/t3code/blob/main/docs/user/composer.md), [t3.codes](https://t3.codes/)) | Git Diff panel with edit in place; no line comments (comments live on artifacts); review artifacts; undo a turn ([Git Diff](https://docs.traycer.ai/panels/git-diff), [review guide](https://docs.traycer.ai/guides/review-agent-changes)) |
| Pull requests | One button to commit, push and open a PR; draft, stacked and amended PRs; GitHub, GitLab, Bitbucket, Azure DevOps, Forgejo, Gitea and GitCafe ([t3.codes](https://t3.codes/), [source control](https://github.com/pingdotgg/t3code/blob/main/docs/user/source-control.md)) | Pull Requests panel (GitHub via `gh`): checks, reviews, "Fix in chat" ([Pull Requests](https://docs.traycer.ai/panels/pull-requests)) |
| In-app browser | Browser tabs belong to the environment; agents keep using them while no device is connected ([remote access](https://github.com/pingdotgg/t3code/blob/main/docs/user/remote-access.md)) | In-app browser agents use while you watch; design mode to mark up the page and send it to the chat ([browsers](https://docs.traycer.ai/panels/browsers)) |
| Visuals in chat | "Visual replies": a sandboxed HTML page (chart, diagram, mockup) in the thread ([visual replies](https://github.com/pingdotgg/t3code/blob/main/docs/user/html-renders.md)) | Live HTML visuals in chat; live HTML wireframes and Mermaid diagrams in artifacts ([wireframes](https://docs.traycer.ai/panels/artifacts/wireframes), [diagrams](https://docs.traycer.ai/panels/artifacts/diagrams)) |
| Remote machines | T3 Connect managed tunnel, LAN or Tailscale pairing, desktop-managed SSH, background service ([remote access](https://github.com/pingdotgg/t3code/blob/main/docs/user/remote-access.md), [background service](https://github.com/pingdotgg/t3code/blob/main/docs/user/background-service.md)) | Remote hosts (other machines running Traycer) from one window; port forwarding; agents message across hosts ([remote hosts](https://docs.traycer.ai/concepts/hosts/remote-hosts), [across machines](https://docs.traycer.ai/guides/work-across-machines)) |
| Scheduled and triggered runs | Built in: scheduled tasks and webhook tasks ([project settings](https://github.com/pingdotgg/t3code/blob/main/docs/user/project-settings.md)) | Command line plus your own cron (documented example); `traycer-autobuild` for long runs ([commands](https://docs.traycer.ai/cli/commands), [artifact workflow](https://docs.traycer.ai/concepts/artifact-workflow)) |
| Usage limits | Usage page (tokens, estimated cost, limits); phone widget; auto-resume when limits reset ([usage](https://github.com/pingdotgg/t3code/blob/main/docs/user/usage.md), [v0.1.0 notes](https://github.com/pingdotgg/t3code/releases/tag/v0.1.0)) | Remaining usage per provider; account switching; optional routing when blocked, off by default ([usage and routing](https://docs.traycer.ai/agents-and-models/usage-limits-and-routing)) |
| Team sharing and roles | Guest links (beta): one person follows one thread in a browser and sends messages you approve; roles and a team plan not documented ([guest links](https://github.com/pingdotgg/t3code/blob/main/docs/user/guest-links.md), [README](https://github.com/pingdotgg/t3code), [docs](https://github.com/pingdotgg/t3code/tree/main/docs/user)) | Share Tasks with Owner, Editor and Viewer roles; artifact comments; team-wide sharing on Sync ([sharing](https://docs.traycer.ai/panels/sharing), [teams](https://docs.traycer.ai/account/teams)) |
| SSO/SAML | Not documented | No ([Teams FAQ](https://docs.traycer.ai/account/teams)) |
| Import existing sessions | Migrates its own V1 threads to V2 ([thread migration](https://github.com/pingdotgg/t3code/blob/main/docs/user/thread-migration.md)) | Imports Claude Code, Codex and OpenCode sessions as Tasks ([first run](https://docs.traycer.ai/first-run)) |
| Telemetry | Product events to `ingest.t3.codes`, forwarded to PostHog; opt out with `T3CODE_TELEMETRY_ENABLED=false` ([telemetry](https://github.com/pingdotgg/t3code/blob/main/docs/user/telemetry.md)) | Sentry and PostHog "may be enabled in release builds"; Privacy Mode, opt-in for individuals ([README](https://github.com/traycerai/traycer)) |
| Maturity (Oct 24, 2026) | About 29,800 stars and 8,000 forks; v0.1.2 stable on October 22, nightlies several times a day; README: "Expect bugs" ([repo](https://github.com/pingdotgg/t3code), [releases](https://github.com/pingdotgg/t3code/releases)) | 11,000+ developers signed in to Traycer Desktop; 40,000+ Tasks created |

## Agents and subscriptions

Neither app resells tokens. T3 Code's site puts it plainly: "T3 Code doesn't resell tokens. ... We orchestrate them, you keep your plan" ([t3.codes](https://t3.codes/)). In Traycer, using Claude Code, Codex, OpenCode or Cursor doesn't consume Traycer credits and carries no markup. The one exception is Auto mode: when its judge is set to Automatic, Traycer's hosted model reviews commands and that uses credits, even in a Claude Code or Codex conversation ([pricing](https://docs.traycer.ai/account/pricing)).

On agent coverage, don't count rows. T3 Code has eight built-in providers, and its ACP Registry route is open-ended: you can add any Registry agent, or a local ACP command ([ACP providers](https://github.com/pingdotgg/t3code/blob/main/docs/user/providers-acp.md)). Traycer documents 22 coding agents and lists, for each one, whether it runs on the Chat interface, the Terminal interface or both, and which permission modes it supports ([coding agents](https://docs.traycer.ai/agents-and-models/coding-agents)).

Both track usage limits. T3 Code's Usage page combines token use, cache savings and estimated API-equivalent cost across providers, and its phone widget shows remaining Codex and Claude quota ([usage](https://github.com/pingdotgg/t3code/blob/main/docs/user/usage.md)). Since v0.1.0 it can resume automatically when limits reset ([v0.1.0 notes](https://github.com/pingdotgg/t3code/releases/tag/v0.1.0)). Traycer shows each provider's remaining usage, switches accounts when one runs low, and can route a blocked chat to another account or an equivalent model. That routing is off by default ([usage and routing](https://docs.traycer.ai/agents-and-models/usage-limits-and-routing)).

## Running agents in parallel

Both use git worktrees. In T3 Code, each thread runs in the current checkout or a new worktree. You can move the worktree folder to another drive, and set automatic cleanup per machine or per project ([project settings](https://github.com/pingdotgg/t3code/blob/main/docs/user/project-settings.md)). Traycer lets you pick Local, New worktree or Existing worktree per folder. A repository can run a setup script in each new worktree and a teardown script before one is removed, and Sweep cleans up idle worktrees while keeping the Tasks and artifacts ([worktrees](https://docs.traycer.ai/concepts/worktrees)).

Both also let agents manage agents, and this is where many older comparisons are out of date. T3 Code's v0.1.0 release added `delegate_task`: an agent starts child agents on any provider or model and waits for their results. The release notes call it "the recommended way to combine harnesses, for example Claude planning and Codex implementing" ([v0.1.0 notes](https://github.com/pingdotgg/t3code/releases/tag/v0.1.0)). Agents that T3 Code didn't start, such as Claude Code in your own terminal or ChatGPT, can connect over MCP and read, start and message threads ([outside agents](https://github.com/pingdotgg/t3code/blob/main/docs/user/outside-agents.md)).

Traycer agents can create child agents, message agents in the same Task, in other Tasks and on your other machines, read each other's transcripts, and claim roles so others can see who owns what ([agent-to-agent](https://docs.traycer.ai/concepts/agent-to-agent)). Both tools do agent-to-agent. What differs is what the agents share.

## Shared plans and context

Traycer is strongest here. Artifacts live on the Task and outlast any one chat. Traycer ships skills that take a feature through brief, core flows, tech plan and tickets. Then `traycer-execute` orders the tickets into batches by dependency, starts one child agent per ticket, and reviews each batch against the plan; product drift stops the run and comes back to you. `traycer-review` writes a review artifact with prioritized findings ([artifact workflow](https://docs.traycer.ai/concepts/artifact-workflow)). Teammates can comment on artifacts ([sharing](https://docs.traycer.ai/panels/sharing)). Plans can also be visual: Traycer's chat shows live HTML visuals of a plan, flow or data, and artifacts hold live HTML wireframes and Mermaid diagrams ([wireframes](https://docs.traycer.ai/panels/artifacts/wireframes)).

T3 Code has the pieces for planning inside a thread: `/plan`, skills from the agent ecosystem, and @-mentioning another thread so the agent can read its history on demand ([composer](https://github.com/pingdotgg/t3code/blob/main/docs/user/composer.md)). When you switch providers, T3 Code passes a budgeted selection of the conversation, 16,000 tokens by default, without the previous provider's reasoning or tool state, and says so up front ([portable handoffs](https://github.com/pingdotgg/t3code/blob/main/docs/user/portable-handoffs.md)). T3 Code also has visual replies: agents can answer with a sandboxed HTML page, such as a chart or mockup, on every provider ([visual replies](https://github.com/pingdotgg/t3code/blob/main/docs/user/html-renders.md)). What we didn't find in its docs, as of October 24, 2026, is a shared spec and ticket layer that several agents work from.

For the thinking behind Traycer's approach, see [our post on spec-driven development](https://traycer.ai/blog/the-ultimate-spec-driven-development-approach).

## Reviewing and shipping changes

**T3 Code wins on the pull-request loop.** One button commits, pushes and opens a PR with a generated title and body. It supports draft, stacked and amended PRs, and works with GitHub, GitLab, Bitbucket, Azure DevOps, Forgejo, Gitea and GitCafe ([t3.codes](https://t3.codes/), [source control](https://github.com/pingdotgg/t3code/blob/main/docs/user/source-control.md)). A review comment from a diff can go straight into your next message to the agent, and **Edit from here** rewinds a conversation, optionally restoring the worktree's files to that point ([composer](https://github.com/pingdotgg/t3code/blob/main/docs/user/composer.md)).

Traycer's review works at a different level. Its Git Diff panel lets you read and edit changed files, and the docs say: "Diffs have no line comments. Comment threads belong to artifacts" ([Git Diff](https://docs.traycer.ai/panels/git-diff)). A second agent can review the change and write a review artifact, and you can undo an agent's turn ([review guide](https://docs.traycer.ai/guides/review-agent-changes)). The Pull Requests panel reads GitHub through `gh` and sends a failing check or a review comment to the agent that wrote the branch with **Fix in chat** ([Pull Requests](https://docs.traycer.ai/panels/pull-requests)).

If your review time goes into lines and PR mechanics, T3 Code is faster. If it goes into checking that the change matches the plan, Traycer fits better.

## Mobile, web and remote machines

**T3 Code wins on browser access.** Both tools have desktop apps and iOS and Android apps in the public stores, and both reach agents on other machines. T3 Code adds a hosted web client at [app.t3.codes](https://app.t3.codes/), so you can drive agents from any browser. It connects through T3 Connect (a managed tunnel), LAN and Tailscale pairing or desktop-managed SSH, and runs as a background service on macOS and Linux (`t3 service install`) ([install](https://github.com/pingdotgg/t3code/blob/main/docs/user/install.md), [remote access](https://github.com/pingdotgg/t3code/blob/main/docs/user/remote-access.md), [background service](https://github.com/pingdotgg/t3code/blob/main/docs/user/background-service.md)). Browser tabs belong to the environment, so agents keep using them while no device is connected. Users single out mobile. One r/codex commenter wrote: "This is the best one I've tried for mobile+codex so far" ([u/dicarli, March 12, 2026](https://www.reddit.com/r/codex/comments/1rn75r5/t3_code_is_out/oa2k8vh/)).

Traycer's mobile app runs the same interface as the desktop and reaches your machines through Traycer's relay. It's on the App Store and Google Play, and it's included on the Free plan ([mobile app](https://docs.traycer.ai/account/mobile-app)). Traycer also works with remote hosts: any other machine running Traycer, added with `traycer host ensure` from its command line. From one window you run agents, terminals and file access on that machine, forward its dev server to your laptop, and let agents message agents there ([remote hosts](https://docs.traycer.ai/concepts/hosts/remote-hosts), [work across machines](https://docs.traycer.ai/guides/work-across-machines)). Its in-app browser has a design mode: mark up the page, pick an element, write what you want changed and send it to the chat ([browsers](https://docs.traycer.ai/panels/browsers)). Traycer has no web app.

## Teams and collaboration

**Traycer wins clearly here too.** You can share a Task by email or GitHub handle with Owner, Editor or Viewer roles, and people can start comment threads on artifacts ([sharing](https://docs.traycer.ai/panels/sharing)). Cloud sync across your own devices and sharing with individual people are free; sharing a Task with a whole team needs the Sync plan ([pricing](https://docs.traycer.ai/account/pricing)). Traycer doesn't support SSO or SAML, as its Teams FAQ says ([teams](https://docs.traycer.ai/account/teams)).

T3 Code's README and docs don't describe roles or a team plan (checked October 24, 2026). Since October 25, a beta guest link lets you share one thread with one person, who follows it in a browser for 24 hours and can send messages that run only when you approve them ([guest links](https://github.com/pingdotgg/t3code/blob/main/docs/user/guest-links.md)). Pairing lets more devices reach one server, but that's device access, not team collaboration. That's "not documented," not "doesn't exist."

## Automation and unattended runs

**T3 Code wins here.** Scheduled tasks run on a fixed schedule, and webhook tasks run when another service calls their URL, such as GitHub on a new pull request or a failed CI job ([project settings](https://github.com/pingdotgg/t3code/blob/main/docs/user/project-settings.md)). Since v0.1.0, queued messages survive restarts and interrupted threads can continue after an update, crash or reboot ([v0.1.0 notes](https://github.com/pingdotgg/t3code/releases/tag/v0.1.0)).

Traycer has no built-in scheduler. Its command line starts Tasks and agents, and the docs show a crontab line that starts one Task a night, using an idempotency key so a double run doesn't start two ([commands](https://docs.traycer.ai/cli/commands)). For long, mostly hands-off work, `traycer-autobuild` drafts a spec, a grading rubric and a way to verify the work, asks you to approve them, then has a builder agent and a separate evaluator agent iterate until the work passes ([artifact workflow](https://docs.traycer.ai/concepts/artifact-workflow)).

## Pricing, license and maturity

Both are free and MIT-licensed. T3 Code has no paid tier. Traycer's Free plan includes your own agents with no token metering, unlimited agent sessions, cloud sync across your devices, sharing with people you invite, remote hosts, the mobile app and agent-to-agent communication. The Sync plan, for sharing Tasks with a whole team, is $20 per user per month, or $16 billed yearly. Optional credits pay for Traycer's own inference at the upstream API price plus 20% ([pricing](https://docs.traycer.ai/account/pricing)).

On maturity: T3 Code had about 29,800 GitHub stars and 8,000 forks on October 24, 2026. Its first stable "Orchestrator V2" release, v0.1.0, shipped October 15, and v0.1.2 followed on October 22, with nightly builds several times a day ([releases](https://github.com/pingdotgg/t3code/releases)). More than 11,000 developers have signed in to Traycer Desktop, and they've created over 40,000 Tasks. Those numbers measure different things, so don't read them as a contest.

Telemetry, briefly: T3 Code sends product-usage events to its own endpoint and on to PostHog, and `T3CODE_TELEMETRY_ENABLED=false` turns that off ([telemetry](https://github.com/pingdotgg/t3code/blob/main/docs/user/telemetry.md)). Traycer's release builds may enable Sentry crash reporting and PostHog analytics, and Privacy Mode governs prompts; it's opt-in for individuals ([README](https://github.com/traycerai/traycer)).

## Which should you choose?

**You're a solo developer who wants to drive agents from a browser and have them fire on a schedule or a webhook.** Use T3 Code. The hosted web app, scheduled and webhook tasks, and the PR button fit that loop.

**You or your team plan a feature, split it into tickets, run agents in parallel and review against the plan.** Use Traycer. Shared artifacts, batched execution and agent-to-agent messaging keep those agents on one plan.

**You're a small team that needs shared work and roles.** Use Traycer. Task sharing with roles and artifact comments are documented; T3 Code documents only a beta guest link for a single thread.

**You want both.** They coexist on plain git worktrees and the same agent CLIs. Plan and coordinate in Traycer, and use T3 Code to approve a run or open a stacked PR from a browser.

## FAQ

### What is T3 Code?

T3 Code is a free, open source (MIT) control plane for coding agents from Theo Browne and team. It runs Codex, Claude Code, Cursor, Grok Build, OpenCode, Antigravity, Pi and Muse Code on your machine and lets you drive them from a desktop app, a web app or its iOS and Android apps.

### Is T3 Code free?

Yes. T3 Code has no paid plan and doesn't resell tokens; you use the agent subscriptions you already have.

### Is Traycer open source?

Yes. Traycer Desktop is open source (MIT); the code is on GitHub at [github.com/traycerai/traycer](https://github.com/traycerai/traycer). The Free plan includes cloud sync for individuals, and the Sync plan ($20 per user per month, or $16 billed yearly) adds team-wide sharing.

### What's the difference between T3 Code and Traycer?

T3 Code is organized around threads on a server you control and is strongest at browser access through its hosted web app, the pull-request loop and scheduled tasks. Traycer is organized around Tasks where several agents share specs, tickets and reviews, message each other across Tasks and machines, and can be shared with teammates.

### Which is better for teams?

Traycer. It lets you share a Task with Owner, Editor and Viewer roles, comment on artifacts and share with a whole team on the Sync plan. T3 Code documents a beta guest link that shares one thread with one person, but not roles or a team plan.

### Can agents talk to each other in T3 Code and Traycer?

Yes, in both. T3 Code's `delegate_task` lets an agent start child agents on any provider. Traycer agents can create child agents, message agents in other Tasks and on other machines, and read each other's transcripts.

### Does T3 Code work on Linux and on phones?

Yes. T3 Code has desktop builds for macOS, Windows and Linux (including AUR packages), a web app, and apps on the App Store and Google Play. Traycer runs on macOS, Windows and Linux, with mobile apps on the App Store and Google Play.

### Is T3 Code better than the Codex app?

T3 Code runs Codex and several other agents in one place and works in a browser; the Codex app is OpenAI's own and runs Codex only.

### Can I use T3 Code and Traycer together?

Yes. Both work on plain git worktrees and the agent CLIs you already have, so you can, for example, plan and coordinate a feature in Traycer and use T3 Code to approve a run from a browser.

## Try Traycer

- [Download Traycer Desktop (free, open source)](https://traycer.ai/download)
- [See how planning, tickets and parallel agents work](https://docs.traycer.ai/guides/plan-a-feature)
- [Share a Task with your team](https://docs.traycer.ai/panels/sharing)