Most coding agents live in exactly one place: whatever terminal you happened to start them in. T3 Code, built by Theo Browne's team at Ping.gg, calls itself an "agent harness control surface" — it doesn't run its own agent, it controls the ones already installed on your machine (Claude Code, Codex, Cursor, Grok Build, OpenCode) from a desktop app, a web app, or a genuinely capable mobile app, so a long-running agent task isn't tied to keeping one terminal window open.
It's a Control Layer, Not Another Agent
The project's own framing in the README is unusually direct about what it isn't: not a new agent, not a hosted service, not something being sold. It authenticates against the CLI tools you already have installed and already pay for — if Claude Code, Codex, Cursor, Grok Build, or OpenCode is set up and authenticated on your machine, T3 Code can control it. That's a meaningfully different starting point than a platform trying to get you onto its own agent or its own subscription; the entire value proposition is the control surface itself; the agents underneath stay exactly what you already chose.
Why the Mobile App Is the Actual Differentiator
Most agent-orchestration tools are desktop-only, which quietly assumes you're at your machine whenever an agent needs a decision. T3 Code ships real iOS and Android apps specifically to break that assumption — you can check on running agents, review what they've done, and send follow-up instructions from your phone. Recent release notes show real investment in that side specifically: a cross-platform mobile usage dashboard, a unified sheet for model and thread settings, work-log parsing that catches provider-specific error patterns, and ongoing polish on how threads and drafts behave on mobile. For anyone kicking off a long agent task and stepping away from the desk, that's the actual gap most competing tools leave open.
Built for Remote and Multi-Environment Work
Beyond the mobile story, the recent changelog shows a system being built for running agents somewhere other than your local machine: worktree selection per project, dev database seeding for worktrees, remote non-Git project support, and a usage page that reads provider transcripts across environments rather than assuming everything runs on one box. Combined with support for five different underlying agent CLIs, the design goal reads clearly: be the layer that works the same way whether an agent is running locally, in a worktree, or on a remote host — a genuinely useful property once a team has more than one machine or environment in the loop.
Why It Exists, In the Team's Own Words
The README answers the obvious skepticism directly, under a section literally titled "Wait, what are you selling me?": nothing. The team says it built T3 Code because it wanted the best possible development experience with agents, and names its actual reference points — the Codex desktop app, Conductor, Claude Desktop, and Cursor Glass — as things that inspired the project but didn't clear its bar. The stated goal is software that's performant, remote-ready, and truly open, with an explicit fallback plan: if the project ever goes the wrong direction, the team wants users to have everything they need to fork it and build the editor they actually want. That's a more concrete standard to hold a project to than typical open-source mission language, and it's worth checking the project against over time rather than taking at face value once.
Getting Started and Provider Setup
T3 Code doesn't run models itself, so before anything works you need at least one underlying agent CLI installed and authenticated: Codex CLI with codex login, Claude Code with claude auth login, Cursor CLI with agent login, Grok Build CLI with grok login, or OpenCode with opencode auth login. Once one of those is set up, the lowest-friction way to try T3 Code is npx t3@latest, which requires Node.js 22.16+, 23.11+, or 24.10+ and launches both the backend and a local web app in your terminal with no separate install step — npx t3@latest --help gives the full CLI reference. The desktop app installs from GitHub Releases or through a platform package manager: winget install T3Tools.T3Code on Windows, brew install --cask t3-code on macOS, or yay -S t3code-bin on Arch Linux via the AUR.
Documentation goes deeper than a typical early-stage README: there are dedicated guides for permission modes, keyboard shortcuts, customizing a project's icon, remote access from a phone or another machine, keeping the app and server in sync as both update, source-control integrations, running multiple accounts for Codex and Claude specifically, and running T3 Code as a background service on Linux. For a project that says outright it's "very very early," that's a meaningfully more complete documentation set than the maturity warning would suggest.
The Release Cadence Shows a Real, Wide Feature Surface
Beyond the correctness fixes already mentioned, recent releases show the product growing on nearly every surface at once: sidebar v2 became the default sidebar, pinned threads can be drag-reordered, a cross-platform mobile usage dashboard shipped, project settings got overhauled into a real settings page with breadcrumbs, worktree selection became per-project, and the desktop app's Browser panel now remembers recently used sites. Mobile-specific fixes are similarly granular — detecting PowerShell cmdlet errors inside work-log rows, stopping Android message bubbles with code blocks from overlapping, fixing long-press-to-navigate behavior on thread rows. That density of small, specific fixes across desktop, web, and mobile in a short window is a reasonable proxy for how much of the app is actually in active daily use by the team building it, not just scaffolded and left alone.
What "Very Early" Actually Means Here
The project is candid about its maturity, and it's worth taking that at face value rather than reading past it. The README states outright: "We are very very early in this project. Expect bugs," and contributions beyond small fixes aren't currently being accepted — this is being built by the core team's own priorities, not shaped by outside PRs yet. The release history backs that up in a good way, though: recent fixes cover real correctness issues like a server-side reaper that was silently killing live background subagents, a greedy agent process that could take down the whole server, and Codex resume handshakes that were completing turns that never actually ran. That's the kind of bug class you only find by running the thing hard in production, which is a reasonable signal of real usage even at an early stage.
Practical Implications
- If you're already running multiple coding agent CLIs, T3 Code's value is entirely in not having to juggle separate terminal sessions and remembering which one is doing what — worth trying specifically if that's already your actual pain point.
- The mobile app is worth evaluating on its own merits for anyone running long agent tasks that benefit from a check-in-and-steer workflow rather than active babysitting.
- "Very early" should be taken seriously before depending on this for anything critical — the project says so itself, and the volume of correctness fixes in recent releases (agents being silently killed, turns completing that never ran) confirms it's still finding real bugs at a meaningful rate.
- Contributions aren't really open yet, so evaluate this as a fast-moving, team-driven product to adopt and report bugs against, not a project to plan on shaping through PRs in the near term.
Practical Takeaway
T3 Code is a focused bet on a specific, underserved layer: not a better agent, but a better way to control the agents you already use, from wherever you actually are — desktop, browser, or phone. For teams already running multiple coding agents day to day, it's worth trying specifically as a control-and-monitoring layer, with the expectation that it's genuinely early software from a team candid about that fact.
Teams evaluating multi-agent control and remote-agent workflows — alongside tools like Orca or Paperclip — can get hands-on architecture help from Woyce Technologies.
FAQ
What is T3 Code?
T3 Code is an open-source "agent harness control surface" from Theo Browne's team at Ping.gg — a desktop, web, and mobile app that lets you control coding agent CLIs you already have installed (Claude Code, Codex, Cursor, Grok Build, OpenCode) from one place.
Is T3 Code its own AI agent?
No — it doesn't run its own agent or model. It controls and monitors CLI agents already installed and authenticated on your machine, using the subscriptions you already have for those tools.
Is T3 Code free to use?
Yes, it's MIT-licensed and open source, installable via npx t3@latest to try without installing, or as a desktop app via winget, Homebrew, or the AUR.
Does T3 Code have a mobile app?
Yes — real iOS and Android apps let you monitor running agents, review their work, and send follow-up instructions remotely, which is a more developed feature than most competing agent-orchestration tools offer.
Is T3 Code stable enough for production use?
The project describes itself as "very very early" and explicitly warns to expect bugs. Recent release notes show active fixes for real correctness issues, which is normal for early-stage software but worth weighing before depending on it for anything critical.
Can I contribute to T3 Code?
The project states it's mostly not accepting contributions yet — small fixes may be considered, but larger features are being driven by the core team rather than the community at this stage.
How do I try T3 Code without installing anything permanent?
Run npx t3@latest in a terminal (Node.js 22.16+, 23.11+, or 24.10+ required). It launches T3 Code's backend and a local web app on your machine without a separate install step.
Do I need a paid subscription to use T3 Code?
T3 Code itself is free and open source. It authenticates against agent CLIs you already have installed and paid for separately — Claude Code, Codex, Cursor, Grok Build, or OpenCode — so your cost is whatever those tools already charge, not an additional T3 Code fee.
Can T3 Code run as a background service?
Yes, on Linux specifically — the project documents running it as a background service, alongside separate guides for remote access from a phone or another machine.
What CLI tools do T3 Code contributors need beyond Node.js?
Contributors need Vite+'s global vp command-line tool (installed via a shell script from vite.plus) and then run vp i to install dependencies — a build-tooling layer separate from the agent CLIs T3 Code itself controls.