T3 Code: Theo Built the Remote Control for Your Agent Fleet
Theo of t3.gg fame has 17,600 stars on a repo he describes as very early and full of bugs, and it hit GitHub trending again today with over 200 new stars. T3 Code is not another coding agent. As Theo put it himself when someone got confused: T3 Code is not a harness, it is an open source app for managing your harnesses.
Here is the setup. You already pay for Claude Code, Codex, Cursor, Grok Build, or OpenCode. T3 Code plugs into those subscriptions with the credentials you already have and gives you one control surface across all of them: a fast mobile app on iOS and Android, a web app, and an Electron desktop app. Kick off an agent from your phone, watch it work, generate a PR with one click. Isolated git worktrees let several agents grind on the same codebase at once without stepping on each other.
The interesting part is where this sits in the stack. For two years the fight was over the harness itself, and that layer is now crowded and fragmenting: everyone has two or three agent subscriptions and no good way to run them side by side. A neutral controller that orchestrates all of them while you keep your existing plans is a genuinely open position, and it explains why an alpha-quality app has 17k stars. The obvious tension: every harness vendor also wants to be your control surface, so the window for an independent one may not stay open long.
MIT licensed, at github.com/pingdotgg/t3code.
← Back to all articles
Here is the setup. You already pay for Claude Code, Codex, Cursor, Grok Build, or OpenCode. T3 Code plugs into those subscriptions with the credentials you already have and gives you one control surface across all of them: a fast mobile app on iOS and Android, a web app, and an Electron desktop app. Kick off an agent from your phone, watch it work, generate a PR with one click. Isolated git worktrees let several agents grind on the same codebase at once without stepping on each other.
The interesting part is where this sits in the stack. For two years the fight was over the harness itself, and that layer is now crowded and fragmenting: everyone has two or three agent subscriptions and no good way to run them side by side. A neutral controller that orchestrates all of them while you keep your existing plans is a genuinely open position, and it explains why an alpha-quality app has 17k stars. The obvious tension: every harness vendor also wants to be your control surface, so the window for an independent one may not stay open long.
MIT licensed, at github.com/pingdotgg/t3code.
Comments