Skip to content

install.md

Latest commit

 

History

History
129 lines (89 loc) · 4.73 KB

install.md

File metadata and controls

129 lines (89 loc) · 4.73 KB
Raw

Install T3 Code

T3 Code is a web and desktop GUI for running coding agents on your machine.

Requirements

Node.js ^22.16 || ^23.11 || >=24.10 on the machine that runs the T3 Code server.

At least one provider CLI, installed and authenticated. See Providers below.

Run Without Installing

npx t3@latest

This starts the T3 Code server on your machine and opens the local web app. Use npx t3@latest --help for the full CLI reference.

Open a project in the desktop app

When the T3 Code desktop app is running on the same machine, open the current directory with:

npx t3 app

Pass a path to open another directory:

npx t3 app ../my-project

The command adds the directory as a project when needed, focuses the desktop app, and opens a new thread. It does not launch the desktop app, open a browser, or start a T3 Code server. A background server does not count as the desktop app. The command also rejects SSH sessions because a remote shell cannot focus a local desktop window. The CLI package and the running desktop app must both include t3 app support.

Desktop App

Download the latest release from GitHub Releases, or install from a package registry.

Windows:

winget install T3Tools.T3Code

macOS:

brew install --cask t3-code

Arch Linux:

Stable:

yay -S t3code-bin

Nightly:

yay -S t3code-nightly-bin

Windows Subsystem for Linux

When the desktop app runs a WSL backend, it installs the matching server runtime into ~/.t3/wsl-runtime inside the selected distro. The first launch after installing or updating T3 Code may take a little longer while that release's runtime is extracted. Later launches reuse the Linux-local copy so startup does not depend on reading application files through /mnt/c. After a successful launch, T3 Code keeps the current runtime and one previous runtime for rollback and removes older caches automatically. If a cached runtime stops working, T3 Code launches from the application files under /mnt/c instead and reinstalls the runtime on the next launch.

Providers

T3 Code drives provider CLIs; it does not ship them. Install the CLI for each provider you want to use, then authenticate it.

Provider CLI Default binary Log in with
Codex Codex CLI codex codex login
Claude Claude Code claude claude auth login
Cursor Cursor CLI cursor-agent agent login
Grok Build Grok Build CLI grok grok login
OpenCode OpenCode opencode opencode auth login

Codex and Claude are on by default. Cursor, Grok Build, and OpenCode are off by default; turn them on in Settings → the provider's card when you want to use them.

Cursor is the one to watch: install Cursor CLI, which provides the cursor-agent binary that T3 Code looks for, but authenticate with agent login, not cursor-agent login.

Grok models that support adjustable reasoning show a Reasoning control beside the model picker. The available levels and default come from the installed Grok Build CLI, so they can vary by model and CLI version.

Run the login command on the machine running the T3 Code server, not on the device you browse from.

Binary Discovery

Each provider CLI must be on the server's PATH, or have an explicit binary path set in Settings → the provider instance → Binary path. Use the explicit path when a version manager or a non-standard install location keeps the CLI off the PATH of the shell that started T3 Code.

When Auth Is Needed

Provider auth is required before you start a session with that provider, not before you start T3 Code. You can install T3 Code, open it, and add providers afterwards. A provider that is not authenticated shows its status in Settings and fails at session start with the login command to run.

For multi-account setups, see Codex and Claude.

Next Steps