Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

T3 Code: drive your agents from your phone

Written November 7, 2026

T3 Code puts Claude Code, Codex, Cursor, and more behind one phone app — 50,000 stars in a week. What it controls, and what stays on your machine.

What it is

T3 Code is an "agent harness control surface" from the T3 Tools team, MIT licensed and free. It is not a model and not a new agent: it drives the coding agents already installed on your machine — Claude Code, Codex, Cursor, Grok Build, OpenCode, Google Antigravity, and fx — through one server with desktop, web, and iOS and Android apps. Each provider has to be installed and signed in first, on the machine running the server. Model use is billed by the provider; T3 Code itself has no API key, no model weights, and no GPU work of its own. The repository passed 50,000 stars, and the maintainers warn the project is very early and to expect bugs.

Version 0.1.7, the current stable release, adds Kiro as an early-access beta provider, managed policies for central administration, one-time schedules, and shareable thread links. The server also exposes an MCP server, so outside agents can operate T3 Code threads.

Setting it up

Install the command line with curl -fsSL https://t3.codes/install.sh | sh, or try it once without installing with npx t3@latest. Then run t3 to start the server and open the local web app. t3 service install keeps it running in the background, and t3 update moves to a newer release. Desktop apps are available through the usual package managers — Homebrew on macOS, winget or scoop on Windows, a .deb on Debian and Ubuntu, the AUR on Arch, and nixpkgs.

On the machine used for this page, the official v0.1.7 release was installed from the project's release files, t3 --version printed t3 v0.1.7, and the server answered HTTP 200 on 127.0.0.1:3773. No agent thread was run from it: no provider CLI on that machine was signed in, and a thread needs one.

Reaching it from your phone

Remote access goes through T3 Connect, the managed route, or through direct pairing on your own network, Tailscale, or SSH. Run t3 up on the host and pick how your other devices reach the machine. A T3 Connect account links up to 3 machines for free. A paired device has full access to the server: it runs agents, edits files, and opens terminals as the server's user, so pairing links should be treated like passwords.

What stays on your machine

Everything the agents touch stays where it is. The server owns files, Git, terminals, and credentials, and the machine has to stay on and reachable for the phone app to do anything. That is the trade for the setup: T3 Code adds a control surface, not a cloud backend, and there is no hosted copy of your code to fall back on when the machine sleeps. The README's own warning is the fair summary — the project is very early, and the server's reach is the thing to respect: anyone who can pair a device can drive the agents on it.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Agent-desktop drives apps via the access tree · Codex 0.167: run parallel sessions in one place · Run three independent lines of research at the same time in Claude Code, then combine the short summaries