T3 Code is a free, open-source app that puts all your coding agents in one window. You keep paying for Claude Code, Codex or Cursor as before; T3 Code is the interface on top: parallel threads, approvals, a diff viewer, a terminal and one button to open a pull request. It runs on macOS, Windows, Linux, the web, iOS and Android, and the phone apps can drive agents on your computer from anywhere.
It's built by Theo Browne (t3.gg) and Julius at T3 Tools, launched in early 2026, and is MIT licensed. The GitHub repo, pingdotgg/t3code , has passed 26k stars. Better Stack's walkthrough is a good 10 minute overview:
What T3 Code is, and what it isn't
T3 Code is not a model and not an agent. It doesn't have its own harness the way OpenCode does. It runs a small server on your computer that starts the official CLIs you already have installed and logged in, and gives them one UI. That has three consequences:
- You get the native harness each model was trained on: Claude Code for Claude, Codex CLI for GPT models.
- Tokens never go through T3 Code. No keys are resold, there are no quota caps, and there's nothing to pay T3 for.
- The work happens on your machine, with your repos, tools and credentials. The desktop app, the browser and the phone are only views of that server. If the machine is off, the agents stop.
Supported agents today: Claude Code , Codex, Cursor, OpenCode, Grok Build and Google Antigravity. All models of all connected agents sit in one picker, so you can switch per thread.
Main features
Parallel threads in isolated worktrees
Each thread can get its own git worktree and branch, so 3 agents can work on 3 features in the same repo without stepping on each other. When a worktree is overkill, the thread works on your local checkout instead. The sidebar shows every thread across projects with its status: working, waiting for approval, waiting for your input, or done.
Permission modes and approvals
Every thread has a permission mode, picked right in the composer:
- Supervised : the agent asks before commands and file changes.
- Auto-accept edits : file edits go through, other actions still ask.
- Auto : the agent's own reviewer approves routine actions and asks about risky ones. Works on Codex, Claude, Cursor and Grok; other agents fall back to asking.
- Full access : no prompts. This is the default for new threads, so switch it in settings if you want the agent to ask first.
When the agent needs permission, the request shows up inline with Approve and Decline, and the thread gets an "Approval" badge in the sidebar. The same request reaches the phone app, so you can approve from anywhere.
Review every turn, revert any message
T3 Code saves a checkpoint around each turn, so the diff panel can show exactly what the latest turn changed, not just everything uncommitted. You can switch to the whole branch or to unstaged changes. If a turn went wrong, revert the conversation to before that message and choose whether to restore the files too.
Next to the diff there's a file browser with an editor, a terminal per thread, and a browser panel for previewing the app the agent is running. Agents can use the same browser tabs, and iOS developers get a live Simulator or Android Emulator panel that the agent can tap through.
Commit, push and open a PR
One button commits, pushes and opens a pull request with a generated description. It works with GitHub, GitLab, Bitbucket, Azure DevOps, Forgejo and Gitea. A Pull requests view shows changes and comments, lets you request reviewers and check out a branch, so you can follow review without leaving the app.
Switch agents mid-thread
You can move a thread from one agent to another, for example plan with Claude and let Codex do the edits. T3 Code hands the conversation over: short threads go across in full, long ones keep the original request, the latest messages and the command results.
Usage and limits
The Usage page reads the history of all your agents and shows tokens, cache savings, a breakdown by model and an estimated API-equivalent cost. The Limits tab shows how much of your subscription's session and weekly limits is left. The cost figures are estimates at API prices, not your actual bill.
Remote access: run agents at home, steer them from your phone
This is the feature that made T3 Code popular. Your laptop or a home server does the work; you start threads, answer questions, approve commands and merge PRs from the phone. The agents keep running while you're away from the desk, and the code never leaves your machine.
4 ways to connect to your machine
| Route | How | Best for |
|---|---|---|
| T3 Connect | Sign in on the host ( t3 connect) and on the phone, pick the machine. No router setup | Easiest, and it enables push notifications |
| LAN pairing | Turn on Network access , scan the QR code or paste the pairing link | At home, on the same Wi-Fi |
| Tailscale HTTPS | t3 serve --tailscale-serve, then t3 pair --tailscale | Your own private network, no third party in the path |
| SSH | In the desktop app: Add environment → SSH , enter user@host | Repos that already live on a Linux server or a Mac mini |
One machine can have several routes, and T3 Code uses the fastest one that answers: the LAN at home, T3 Connect or Tailscale when you're out. After you pair once through T3 Connect, it learns the machine's LAN and Tailscale addresses on its own. In a browser, app.t3.codes connects to the same machines, as long as they have an HTTPS address.
What you can do from the phone
The iOS and Android apps aren't a read-only dashboard. You get the full loop:
- One inbox of threads across all your machines, with what needs you at the top
- Chat with the agent and attach images
- Review the diff and approve or merge
- A real terminal on the remote machine, with port forwarding for previewing a dev server
- Push notifications when an agent finishes, fails or needs approval, and Live Activities on the lock screen (iOS) or ongoing notifications (Android)
Keep the machine available
For the phone to be useful, the server has to keep running when you close the terminal. On macOS and Linux,
t3 service install sets it up as a background service, and t3 update keeps it current. With 2 or more machines connected, T3 Code can spread new threads across them by free CPU and memory. A laptop can also run in remote-only mode: no local agents, it just drives the machines elsewhere.Other agents can use your machine too. Each environment has an MCP endpoint, so Claude Code in your terminal, ChatGPT or a bot can start and message T3 Code threads after you approve them.
Security
A pairing link is a password: whoever opens it can run commands on your machine. Each new device needs a fresh one-time link, and you can revoke a device or limit what a link allows (read only, no file writes, no git pushes) in Settings → Connections . T3 Connect relays only the connection setup; after that, traffic goes straight to your machine through a Cloudflare tunnel. If you'd rather keep a managed service out of the path entirely, use LAN, Tailscale or SSH.
How to set it up
- Install and log into at least one agent CLI:
claude,codex,cursor-agent,opencodeor Grok's CLI. For Codex, T3 Code can also sign you in with your ChatGPT account.
- Install T3 Code:
- Try it without installing (Node 22.16+):
npx t3@latest
- Install script:
curl -fsSL https://t3.codes/install.sh | sh
- Desktop app: download from t3.codes , or
brew install --cask t3-codeon macOS,winget install T3Tools.T3Codeon Windows,yay -S t3code-binon Arch
- A setup wizard walks through 3 steps: pick the computers to use, check which agents are ready, and import your projects. It finds the projects and past conversations of the agents you already use, so you can bring them over in one click.
- Set the default permission mode in Settings → General before the first real task.
- For the phone: install the iOS or Android app and connect through one of the routes above.
Where it falls short
T3 Code is still alpha, at version 0.0.45 stable with daily nightlies, and the README says to expect bugs. Settings move between releases, and server and phone app need compatible versions.
Each agent still has its own install, login and update cycle, and you manage all of them. Usage numbers are estimates read from local history, not your bill, and they're only as complete as that history. Remote access only works while the host is on and reachable, so a laptop that sleeps in a bag isn't a server. And a permission mode is not a sandbox: in Full access, the agent can do anything your user account can.
T3 Code alternatives: Conductor, Superset, Herdr and official apps
Conductor has the more polished UX but is closed source and built around Claude Code first. The official Claude Code and Codex desktop apps go deepest on their own models but lock you into one provider. Superset is the closest open-source alternative, with a built-in browser and terminal. T3 Code's edge is the combination: open source, every major agent, and real mobile apps that drive your own machine. If you'd rather stay in the terminal, Herdr runs the same agents in real terminal panes and keeps them alive over SSH. For a side-by-side of all of them, see Top new agentic IDEs .
Ship faster than your competition
Focus on customers and sales while we handle product delivery. Hire a dedicated AI maker or a whole product team.
Launch new products
Fix your delivery
Hit fundraising milestones
















