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

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 (external site)).
• 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 (external site), source control (external site)).
• 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 (external site)).
• Want parallel agents to work from the same specs, tickets and reviews instead of separate chat histories (artifact workflow (external site)).
• 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 (external site)).
• Need teammates to see, comment on and steer agent work (sharing (external site)).

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 (external site), repo (external site)). 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 (external site)).

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 (external site), ACP providers (external site)). 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 (external site), repo (external site)). 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 (external site)). 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.

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 (external site)). 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 (external site)).

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 (external site)). 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 (external site)).

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 (external site)). Since v0.1.0 it can resume automatically when limits reset (v0.1.0 notes (external site)). 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 (external site)).

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 (external site)). 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 (external site)).

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 (external site)). 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 (external site)).

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 (external site)). 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 (external site)). Teammates can comment on artifacts (sharing (external site)). 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 (external site)).

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 (external site)). 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 (external site)). 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 (external site)). 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.

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 (external site), source control (external site)). 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 (external site)).

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 (external site)). A second agent can review the change and write a review artifact, and you can undo an agent's turn (review guide (external site)). 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 (external site)).

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 (external site), 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 (external site), remote access (external site), background service (external site)). 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 (external site)).

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 (external site)). 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 (external site), work across machines (external site)). 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 (external site)). 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 (external site)). 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 (external site)). Traycer doesn't support SSO or SAML, as its Teams FAQ says (teams (external site)).

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 (external site)). 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 (external site)). Since v0.1.0, queued messages survive restarts and interrupted threads can continue after an update, crash or reboot (v0.1.0 notes (external site)).

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 (external site)). 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 (external site)).

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 (external site)).

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 (external site)). 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 (external site)). Traycer's release builds may enable Sentry crash reporting and PostHog analytics, and Privacy Mode governs prompts; it's opt-in for individuals (README (external site)).

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#

Try Traycer#

• Download Traycer Desktop (free, open source)
• See how planning, tickets and parallel agents work (external site)
• Share a Task with your team (external site)