T3 Code Unifies Every Coding Agent Under One Control Panel
For developers juggling several AI coding clients, T3 Code removes the need to switch windows and import projects repeatedly. It standardizes agent interoperability through ACP, which means the same control panel can drive code agents from any vendor, and it lets teams parallelize work across different models without file conflicts.
T3 Code, built by Theo Browne's Ping Labs and released under MIT, positions itself as an "Agent Harness Control Surface." Instead of aggregating model APIs or acting as a token reseller, it takes over the official CLIs and agents already installed and logged in on your machine. Claude Code, Codex, Qoder, Kimi, DeepSeek, and others keep running on their own harnesses, so you avoid the compatibility bugs that come from shimming models into foreign harnesses.
The project brings cross-agent orchestration, Git Worktree isolation, and remote mobile control via Tailscale or its own T3 Connect tunnel. It scans local project paths and imports existing threads from other coding agents. A built-in internal /mcp endpoint lets a main thread delegate subtasks to different agents, each in its own worktree, and collect results back for review and merging. The server runs on Bun and talks to the frontend over WebSocket and JSON-RPC, with a React/Vite web UI and Electron desktop shell.
A notable workflow test showed multiple agents fixing separate bugs in parallel, a third agent verifying fixes, and a final agent reviewing and merging, all within one main thread. T3 Code also handles Git operations like diff, commit, push, and PR creation from the right panel. For Gemini users, T3 Code uses Google's official antigravity-acp server through the ACP protocol, making it the first stable way to use Gemini with personal OAuth without getting banned by reverse proxies.
The BYOS approach shifts value from model access to orchestration, so T3 Code monetizes through convenience rather than taking a cut on API tokens.
Because T3 Code delegates to official CLIs, it sidesteps the fragile model-harness compatibility layer that many relay clients suffer from.
Standardizing on ACP means Google, OpenAI, and others can make their agents interoperable, which may reduce vendor lock-in for coding agents.
Git Worktree isolation turns parallel AI development into a safe operation, making it practical to run several agents on the same repository without branch conflicts.
The internal /mcp delegation endpoint turns any agent into a worker in a larger orchestrated pipeline, which is a pattern likely to spread beyond coding agents.
The pain point of switching back and forth is spot on; having each Agent with its own client is indeed fragmented. What impressed me most is the positioning of not selling tokens and only being the control layer; BYOS is quite restrained. The feature of remotely checking progress on your phone also looks pretty practical.