T3 Code
T3 Code is a local GUI for Codex, Claude Code, Cursor, Grok Build, OpenCode, and Antigravity. It runs provider agents on your machine and lets web, desktop, and mobile clients control them.
This repository is the tarik02-org fork of T3 Code. It stays compatible with upstream clients and data while carrying a small set of product changes and its own release pipeline. See FORK.md for the maintained behavior and ownership rules.
Fork goals
- Keep long conversations fast without transferring or rendering the whole thread on every update.
- Prefer small, self-contained changes that can be replayed on current upstream code.
- Base stable releases on explicit upstream stable commits.
- Publish first-party Nix, desktop, and web artifacts.
Compatibility
- Upstream clients can use the fork server, and fork clients can use upstream servers.
- Existing upstream RPC contracts remain compatible.
- Fork-only RPCs are optional and advertised before clients use them.
Maintained changes
- Frontmatter rendering in web and mobile previews.
- Unsigned macOS updates and isolated canary desktop state.
- Thread-scoped launch environment identity for providers and terminals, with a read-only
t3_identity MCP tool when shell environment injection is unavailable, such as Cursor's local SDK.
- Nix packaging and stable, nightly, and manually managed canary releases.
Installation
Install and authenticate at least one supported provider before starting T3 Code.
Release artifacts
Desktop builds for macOS, Linux, and Windows, plus hosted web archives, are available from GitHub Releases. Desktop builds are unsigned, so the operating system may ask you to approve them on first launch.
Headless CLI archives are available for macOS arm64, Linux x64, and Windows x64. Extract the archive and run t3 or t3.exe from it. The archives include the runtime and web client, so Node.js is not required.
Nix
The Nix flake currently supports x86_64-linux and exposes t3code-desktop and t3code-headless packages.
Development
Install Vite+, then install the workspace dependencies:
vp i
Read MAINTENANCE.md before changing fork history or release state. Read CONTRIBUTING.md before opening an issue or pull request.
