T3 Code runs coding agents on your computer and lets you control them from its desktop, web, or mobile app. Set up the machine where the agents will work first.
You need an installed, authenticated provider before starting a thread. You can launch T3 Code and configure providers afterwards.
curl -fsSL https://t3.codes/install.sh | shOn Windows, in PowerShell:
irm https://t3.codes/install.ps1 | iexThis puts t3 in ~/.local/bin. If your shell reports command not found
afterwards, that directory is not on your PATH yet; the installer prints the
line to add. Set T3CODE_CHANNEL=nightly to install the nightly train, or
T3CODE_VERSION to pin an exact version.
| Task | Command |
|---|---|
| Start the server and open the web app | t3 |
| Start the server without a browser | t3 serve |
| Keep it running in the background (macOS, Linux) | t3 service install (details) |
| Move to the newest release | t3 update |
| Remove it again | t3 uninstall |
Run t3 --help for the full reference.
To try T3 Code once without installing it, run npx t3@latest instead (needs
Node.js for npx).
There is no t3 executable for Intel Macs (the desktop app is available). To
run a server there, build it from source with Node.js 24 and vp
(Install vp):
git clone https://github.com/pingdotgg/t3code
cd t3code && vp i && vp run build:desktop
node apps/server/dist/bin.mjst3 update and the background service do not apply to a server run this way;
update it with git pull and a rebuild.
Download a release from GitHub Releases, or use a package manager:
| Platform | Install |
|---|---|
| Windows | winget install T3Tools.T3Code |
| macOS | brew install --cask t3-code |
| Arch Linux | yay -S t3code-bin |
| Arch Linux nightly | yay -S t3code-nightly-bin |
Choose a WSL distro in Settings → Connections to run agents and projects there. Install the provider CLIs inside that distro. T3 Code installs its own server runtime there automatically; the first launch after an app update can take longer.
With the desktop app already running on the same machine:
t3 appThis opens a new thread for the current directory, adding the project if needed.
Pass a path, such as t3 app ../my-project, to open another directory. It requires
the desktop app, so a standalone server or an SSH session is not enough. If the
command cannot reach the app, start or update the desktop app and try again.
Install T3 Code from the App Store or Google Play. The phone connects to a server on another machine. Follow remote access to link it through T3 Connect or a pairing URL.
If the app crashes during launch, open Settings → Diagnostics on the next launch that succeeds. It lists startup crashes from the last 7 days with the error and component stack that store crash reports leave out. Copy the report and paste it into a GitHub issue. Error messages can quote values from the app, so read it over before sharing.
Open Settings → Providers in the web or desktop app, select the environment, and enable the provider you want. Installation, login, and configuration belong to that environment's machine, even when you connect from a phone or another computer.
| Provider | Install and authenticate |
|---|---|
| Codex | Install Codex CLI, then run codex login. |
| Claude | Install Claude Code, then run claude auth login. |
| Cursor | Install Cursor CLI, then run agent login. |
| Grok Build | Install Grok Build CLI, then run grok login. |
| OpenCode | Install OpenCode, then run opencode auth login. |
| Antigravity | Install and sign in with Google from T3 Code's provider settings. |
Provider CLIs must be on the server's PATH. If T3 Code cannot find one, set its
Binary path in provider settings, especially when using a version manager.
Cursor's executable is cursor-agent, although its login command is
agent login. Antigravity can use its managed runtime without a PATH entry.
When a provider CLI is behind its latest release, its provider card shows the available version. Update now appears only when T3 Code can tell which installer owns the CLI (its own update command, Homebrew, or a global npm, pnpm, bun, or Vite+ install) and runs that installer. Otherwise update the CLI the same way you installed it. Homebrew installs compare against the version Homebrew offers, which can trail the npm release by a few hours.
Add another provider instance for a separate account or configuration. Each instance can have its own environment variables, such as API keys or a custom base URL. Mark secret values as sensitive; after saving, T3 Code does not display their original values.
For provider-specific setup and accounts, see Codex, Claude, OpenCode, and Antigravity.
- Working with threads: start tasks and organize parallel work.
- Permission modes: choose when agents ask before acting.
- Remote access: connect from another device.
- Running in the background: keep a Linux or macOS host available.
- Updating T3 Code: update the app and connected servers.