Skip to content

T3 Code ​

Advanced An agent harness control surface — drive Claude Code, Codex, Cursor, Grok Build, or OpenCode running on one machine from a phone, browser, or another desktop.

Source of truth ​

Repo: github.com/pingdotgg/t3code
Web app: app.t3.codes

Early software

The project describes itself as "very very early" — expect bugs, and it currently discourages contributions beyond small fixes.

Why use it here ​

The other two pages on this section move ports. T3 Code moves the agent session: your desktop keeps running the CLI agent with your repos, tokens, and worktrees, and you steer it from wherever you are.

LayerWhat it does
ProvidersClaude Code, Codex, Cursor, Grok Build, OpenCode (install + auth them first)
ServerRuns where the code lives
ClientsiOS / Android app, web app, Electron desktop

Run it ​

Fastest path — no install (needs Node 22.16+, 23.11+, or 24.10+):

bash
npx t3@latest

Desktop app:

powershell
winget install T3Tools.T3Code
bash
brew install --cask t3-code    # macOS
yay -S t3code-bin              # Arch (AUR)

Remote access ​

Pair a running server ​

bash
npx t3 pair                # fresh pairing token + QR code, no restart
npx t3 pair --tailscale    # publish over Tailscale Serve HTTPS and pair via that URL

--tailscale is the answer for a loopback-only server: it pairs through https://YOUR-MACHINE.YOUR-TAILNET.ts.net/ instead of exposing a port.

Headless server ​

bash
npx t3 serve --host "$(tailscale ip -4)"   # bind to the tailnet address
npx t3 serve --tailscale-serve             # Tailscale HTTPS pairing

The server prints connection strings, pairing tokens, URLs, and QR codes.

Desktop app ​

Settings → Connections → toggle Network access under "This environment", then Create Link for a shareable pairing link.

SSH launch ​

Settings → Connections → Remote Environments → Add environment → SSH flow, target [email protected]. The app starts the server and handles port forwarding for you.

Credentials ​

bash
t3 auth --help    # issue credentials, inspect sessions, revoke access

Treat pairing URLs as passwords

Anyone holding a pairing URL or token can drive a coding agent that has your repo checkouts and provider credentials. Bind to trusted private addresses (tailnet) rather than public ones, and revoke via t3 auth the moment a link leaks.