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.
The @rtvision/t3 npm package runs on Node.js 22.16+ in the 22.x line,
23.11+ in the 23.x line, or 24.10 and later. Install Node.js and npm on the
server and connect to RTVision's network to reach its npm registry. The desktop
app includes its server runtime.
SSH hosts use a standalone archive when it is available and compatible. Hosts such as Alpine need Node.js and npm for the fallback installation.
You need an installed, authenticated provider before starting a thread. You can launch T3 Code and configure providers afterwards.
npx --registry=https://npm-registry.rtvision.com/ @rtvision/t3@latestThis starts the server and opens the local web app. Run
npx --registry=https://npm-registry.rtvision.com/ @rtvision/t3@latest --help for command-line options.
To start in a new working directory, use an explicit path such as t3 ./my-project.
A bare directory name is accepted only if it already exists. If t3 or t3 start
reports an already running server, connect to it, stop it before starting a replacement,
or use a different --base-dir for an independent server.
Download the Windows x64 or Linux x64 installer from RTVision GitHub Releases. Desktop installers are unsigned.
The desktop app includes the t3 command-line tool. To run it from any
terminal, open Settings → General → About and choose Install next to
t3 command. On macOS and Linux it adds a t3 link to a folder on your
PATH; on Windows it adds the app's command folder to your PATH. Open a new
terminal afterwards. Remove takes it off again. If you already have t3
from npm, it stays as it is.
Choose a WSL distro in Settings → Connections to run agents and projects there. Install and authenticate provider CLIs inside that distro. T3 Code installs its matching server runtime there automatically; the first launch after an app update can take longer.
The bundled Linux runtime needs libatomic.so.1. On Debian or Ubuntu, install
it inside the WSL distro with sudo apt-get update && sudo apt-get install libatomic1.
If a startup failure switched the app to Windows, re-enable the WSL backend in
Settings → Connections after installing the library.
With the desktop app already running on the same machine:
npx --registry=https://npm-registry.rtvision.com/ @rtvision/t3 appThis opens a new thread for the current directory, adding the project if needed.
Pass a path, such as npx --registry=https://npm-registry.rtvision.com/ @rtvision/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.
Nightly builds need the beta app. The store apps cannot connect to them. A Nightly build also shows these links as QR codes in Settings → General → Mobile app.
- iPhone and iPad: join the TestFlight beta.
- Android: join the beta group. With the same Google account, open the Google Play testing page and become a tester.
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 | Connect with ChatGPT, or install Codex CLI and 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. |
| Pi | Install Pi, then run pi once to finish its login or API-key setup. |
| Muse Code | Install Muse Code on the server, run muse login, then enable it in Settings → Providers. |
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. Codex connected through ChatGPT and Antigravity can use their
managed runtimes without a PATH entry.
T3 Code warns when a provider version has known compatibility problems with your release. Check Settings → Providers on that environment for the recommended version or range. When its package manager supports installing a specific version, you can install the recommendation there. Otherwise use the provider's installer on the environment's machine. An unlisted version is unverified.
When a provider CLI is behind its latest release, its provider card shows the available version. Update now runs the installer that owns the CLI (Homebrew, or a global npm, pnpm, Yarn, Bun, Volta, or Vite+ install), or the CLI's own update command when T3 Code cannot tell. Update a CLI installed with mise through mise. Cursor and Antigravity update with T3 Code. 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, Antigravity, Pi, and Muse Code.
- 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.