Install T3 Code

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.

Requirements

Command-line use, SSH hosts, and WSL backends need Node.js 22.16+ (22.x), 23.11+ (23.x), or 24.10 and later. The native desktop app includes its server runtime.

You need an installed, authenticated provider before starting a thread. You can launch T3 Code and configure providers afterwards.

Run without installing

This starts the server and opens the local web app. Run npx t3@latest --help for command-line options.

Desktop app

Download a release from GitHub Releases, or use a package manager:

Windows Subsystem for Linux

Choose a WSL distro in Settings → Connections to run agents and projects there. Install Node.js and provider CLIs inside that distro. T3 Code installs its matching server runtime there automatically; the first launch after an app update can take longer.

Open a project from a terminal

With the desktop app already running on the same machine:

This opens a new thread for the current directory, adding the project if needed. Pass a path, such as npx 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.

Mobile app

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.

Providers

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 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.

Next steps

• 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.