Your coding agent is running on your desktop. You are not at your desktop. That gap — between the machine where the work happens and the person who has to approve the next step — is the whole problem T3 Code exists to close.
T3 Code is an open-source “agent harness control surface” from the T3 Tools team (the repo is pingdotgg/t3code on GitHub, MIT licensed). It is not a model. It is not a new coding agent. (If you are still choosing between the agents themselves, start with our Claude Code vs Cursor comparison – this piece is about what sits on top of whichever one you picked.) It is a small server that runs on the machine where your agents already live, and it remote-controls the ones you already pay for: Claude Code, Codex, Cursor, Grok Build, OpenCode, Google Antigravity, and fx. A phone app, a web app, a desktop app, and a terminal command all drive the same threads.
The demand is not subtle. The repository passed 50,000 stars this week — 50,470 when we read it on the morning of November 7, 2026, up more than 16,000 in the week to November 6, the largest weekly gain of any AI project on GitHub. It was created in February 2026. Nine months from zero to fifty thousand stars is what a widely felt gap looks like when somebody finally fills it.
What it actually does
Install the t3 command on the host machine, connect at least one provider using that provider’s own login (claude auth login, codex login, agent login for Cursor — Antigravity needs no CLI; you enable it in Settings and sign in with Google), and start the server. It listens on your machine, port 3773 by default. Register a project, start a thread, and the agent works in that project exactly as it would if you were sitting there.
From that point you have four ways to reach the same work:
- The phone app (iOS and Android, free) — start runs, watch threads, approve a step or send a correction, browse files, review diffs, run version-control actions, use the terminal. The Android listing describes it as “pretty much the full power of the desktop app.”
- The web app — the same surface in a browser.
- The desktop app — Electron, on Windows, macOS, and Linux.
- The
t3CLI itself —t3 thread start,t3 thread send,t3 thread listfrom any terminal. A thread waiting on you exits with its own signal, so scripts can tell “finished” apart from “blocked on the human.”
Two connection routes matter. On your own network — or over a private network like Tailscale — you pair a device directly with a one-time link or QR code, no account at all. Away from home, T3 Connect is the managed relay: no router configuration, sign in on the host, sign in on the phone, pick your machine. Per the hands-on guide we worked from, a free T3 Connect account links up to 3 machines.
Every thread writes to its own branch. When the work is good, one button opens the pull request on GitHub with a generated title, body, and changelog — after you’ve reviewed the diff inline. The agent does the typing. You keep the merge.
What it costs
Nothing for the software. T3 Code is free and MIT licensed — “If you don’t like something, fork it” is a headline feature on its own site, with the fork command printed under it. It does not resell tokens and it does not hold your credentials hostage: you bring your existing subscriptions, log in with each provider’s own flow, and model usage is billed by your provider exactly as before. “Bring your own sub. No keys resold. No quota caps.”
That pricing shape is the point. The control layer is becoming a commodity; the subscriptions underneath it are the spend. A control plane you can fork can never raise its rent on you.
The honest limits
The README says it in plain words: “We are very very early in this project. Expect bugs.” Believe it. The stable release this week is v0.1.7. This is a fast-moving, nine-month-old project, not settled infrastructure, and the team is mostly not accepting contributions yet.
Three operational limits follow from the design:
- The host has to stay awake. Your agents run on your machine, not in T3 Code’s cloud. On Linux and macOS you can install the server as a background service (
t3 service install). Windows gets no background service — you leave the desktop app running, and closing its last window stops the local server. - Remote access is a security decision, not a default. On a local network, the pairing code is the only thing between your agents and every other device on that network. Pair per device with fresh one-time links, don’t enable LAN access on a network you don’t trust, and prefer a private network like Tailscale for anything beyond the couch.
- It controls agents; it doesn’t supervise them. T3 Code moves the approval to your phone. It does not decide whether the work order was well-specified, whether the agent’s output is right, or whether the diff should merge. That judgment problem is the same one behind our MCP tool-poisoning checklist: the harness around the agent is where the safety lives. The judgment layer is still yours.
How this maps onto a multi-seat shop
We run several agent seats — Claude, Cursor, Antigravity, Grok — and the standing problem with seats is presence. Work stalls at approval points because the human isn’t at the keyboard the agent is attached to. Anyone who has watched a finished piece of work sit idle for hours because it was waiting on a tap that could have happened from a phone knows this stall by name.
Against that setup, T3 Code is a fit in three specific places:
- It covers the seats we actually run. Claude Code, Cursor, Antigravity, and Grok Build are all on its provider list today. One surface over all of them beats four vendor apps with four different ideas about remote access.
- It keeps the work on our hardware. The alternative shape — cloud agents that keep running while your machine sleeps — means your code and data live on the vendor’s machines by design. T3 Code’s answer is the opposite trade: your machine stays the plant, and the phone is just the window into it.
- It matches how the work is already shaped. Bounded task per thread, worktree or branch isolation for unreviewed work, diff review before merge — that’s the same discipline as a work order with receipts. The remote control doesn’t change the discipline; it removes the geography from it.
Where it doesn’t fit is just as clear. It doesn’t replace the harness — the work orders, the context, the QC on what comes back. A remote control for a badly briefed agent just lets the agent be badly briefed from further away. And for work that genuinely has to run while every machine you own is off, a self-hosted control surface is the wrong tool no matter how good the app is.
The verdict
Real, and early. The star count is the loudest signal, but the quieter one is the shape: open source, multi-provider, your hardware, your subscriptions, forkable if the team ever takes it somewhere you don’t want to go. That is the correct shape for a control layer, and it’s the shape the closed vendor apps don’t offer.
Try it the cheap way: one machine, one provider you already pay for, one bounded thread started at your desk and approved from your phone. If that loop feels like the missing piece, it earns a place. If it doesn’t, you’ve spent ten minutes and nothing else — which, for a tool at version 0.1.7, is exactly the right size of bet.
Sources: the T3 Code repository and README (github.com/pingdotgg/t3code — 50,470 stars, 9,813 forks, MIT license, repo created February 8, 2026; read November 7, 2026); t3.codes (positioning, provider list, fork-it terms; read November 7, 2026); AI Frontier Post hands-on tutorial, “T3 Code: drive Claude Code, Codex and Cursor from your phone” (install, pairing, service, and T3 Connect machine-limit details, verified end-to-end by its author against v0.1.7; published November 7, 2026).