T3 Code, the long version

What you are getting

• One interface, many agents. Claude Code, Codex, Cursor, Grok Build, Kiro, OpenCode, Antigravity, Pi, Muse Code and fx.
• Your subscriptions, not theirs. T3 Code drives the CLIs you already signed in to. It does not resell tokens.
• A branch per thread. Each agent thread writes to its own git branch, and one button commits, pushes and opens the pull request.
• Everywhere. A desktop app, a web app, and mobile apps that connect to a server on another machine.
• MIT licensed. Fork it, change it, host it yourself.

Install the t3 command

curl -fsSL https://t3.codes/install.sh | sh

irm https://t3.codes/install.ps1 | iex

npx t3@latest

• The binary goes in ~/.local/bin. If that folder is not on your PATH, the installer prints the line to add for zsh, bash or fish.
• On Windows, t3 works at once in the same PowerShell window. Add the folder to PATH for new windows.
• If a t3 it did not create already exists, the installer leaves it alone and stops.
• Set T3CODE_CHANNEL=nightly for the nightly channel, or T3CODE_VERSION to pin a version.

Intel Macs

There is no t3 executable for Intel Macs. The desktop app works. To run a server you build from source, and t3 update and the background service do not apply:

git clone https://github.com/pingdotgg/t3code
cd t3code && vp i && vp run build:desktop
node apps/server/dist/bin.mjs

Or install the desktop app

• The desktop app sets up the t3 command on first launch. Reinstall it from Settings, About.
• WSL: pick a distro in Settings, Sharing & access, and install your provider CLIs inside that distro. T3 Code installs its server runtime there itself.
• .deb: the app updates itself and asks for your password each time. No prompt means the update failed, so install the new .deb by hand.
• Nix: needs Nix 2.30 or later with flakes. Update through Nix, never through the in-app updater or t3 update.

Driving it from your phone or another machine

The mobile app does not run agents. It connects to a server on a real computer. There are two ways to make that connection.

T3 Connect: no router fiddling

1. On the host, run t3 up and choose T3 Connect. On the desktop app, sign in under Settings, Sharing & access, and turn T3 Connect on.
2. On the other device, sign in to the same T3 Connect account and pick the machine.

Signing in over SSH prints a link and a short code. Open the link on any device, check the code matches, and approve. Each account can link 3 machines. Phones and browsers do not count. T3 Chat Pro raises that to 10, and Premier to 100.

Direct pairing: your own network

t3 up --lan
t3 pair

Scan the QR code or paste the pairing URL under Add environment on the other device. This accepts connections from your local network and tailnet, and T3's docs are blunt about it: the pairing code is the only protection. Use a fresh one-time link for each device.

Tailscale HTTPS

t3 serve --tailscale-serve
t3 pair --tailscale

Both devices on the same tailnet. Pairing URLs look like https://machine.tailnet.ts.net/. If port 443 is taken, use --tailscale-serve-port.

SSH, managed for you

In the desktop app: Settings, Environments, Add environment, SSH, then a host such as user@example.com. T3 Code starts or reuses a server there and sets up the port forward. The remote host must be Linux or an Apple Silicon Mac. Check your provider CLIs are visible to a non-interactive shell first:

ssh user@example.com 'sh -lc "command -v claude codex"'

The mobile app itself

Store links and QR codes live in Settings, About, Mobile app. T3's install page points to the App Store and Google Play, and also describes an invite-only TestFlight for iPhone and iPad and beta APKs for Android on GitHub. Use whatever that settings page hands you.

Keeping it running

t3 service install
t3 service status
t3 service restart
t3 service uninstall

• LinuxNeeds systemd user services. Setup turns on lingering so the service starts at boot and survives logout. If it dies when your SSH session closes, run sudo loginctl enable-linger "$(id -un)". t3 service protect reserves memory so agents cannot starve the server.
• macOSStarts at login and stops at logout. For unattended access the Mac has to stay logged in and awake. If agents cannot reach Desktop, Documents or Downloads, grant Full Disk Access to the t3 executable.
• WindowsNo background service. Keep the desktop app open with its local environment on, or leave t3 serve running in a terminal. Minimize the app. Do not close its last window.

Your projects, threads and settings live under ~/.t3/userdata and survive an uninstall. Custom environment variables go in ~/.t3/service.env as plain KEY=VALUE lines; restart the service after editing, and chmod 600 the file if it holds credentials.

Updating without tears

• The update button at the bottom of the sidebar updates every connected machine in one go: outdated providers first, then servers, then the desktop app.
• From a terminal: t3 update. Add a version to pin one, --channel nightly to switch trains, --allow-downgrade to go backwards.
• Switch Stable and Nightly in Settings, About, Update track.
• App and server must speak the same protocol version. If they do not, the connection is refused and a notice names the side to update.
• Updates interrupt running agents and terminal commands. Saved threads, settings and files remain, and “Continue threads after restarts” is on by default.

Sources: t3.codes and T3 Code's own documentation at github.com/pingdotgg/t3code (install, remote access, background service and updating guides), read on November 11, 2026. T3 Code is not made by Anthropic or by us, it is early software, and it changes fast. When this page and their docs disagree, their docs win. See also the other third-party apps.