T3 Code is a minimal web GUI for coding agents made by Pingdotgg. This project is a downstream fork of the original T3 Code, maintained in aaditagrawal/t3code.
This fork focuses on expanding provider support, keeping usage and limit monitoring visible, improving persistence layers, and refining provider management across the app. The current branded release is T3 Code v0.0.36 — ACP Edition.
Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, OpenCode, Google Antigravity, and the other supported agents below. If they're set up on your computer, T3 Code can control them.
It supports configurable stdio ACP agents, Codex, Claude Code, Cursor, Droid, Fx, Grok Build, OpenCode, Antigravity, Amp, Copilot, Gemini CLI, Hermes Agent, Kilo, Oh My Pi, Pi, and Prime Agent.
(NOTE: Amp /mode free is not supported, as Amp Code doesn't support it in headless mode - since they need to show ads for that business model to work.)
This fork uses separate application identifiers and state so both builds can run on the same machine.
| Identifier | This fork | Upstream |
|---|---|---|
| State directory | ~/.t3code-fork |
~/.t3 |
| Default server port | 3873 | 3773 |
| CLI binary | t3f |
t3 |
| Desktop/mobile app ID | com.t3tools.t3code.fork |
com.t3tools.t3code |
| Desktop profile directory | t3code-fork |
t3code |
| URL scheme | t3code-fork:// |
t3code:// |
| Linux service | t3code-fork.service |
t3code.service |
| macOS service | com.t3tools.t3code.fork.service |
com.t3tools.t3code.service |
Existing fork data is imported when a previous home has a recognized, compatible fork database. The import prefers statev2.sqlite and otherwise uses state.sqlite. Upstream-only or incompatible databases are left in place. The import copies state and retains a symlink to existing worktrees. Keep the previous home after upgrading so those worktrees remain accessible. See upgrading the fork for details.
This fork aims to provide a more robust and feature-rich multi-provider experience, with improved server management, visible usage/rate-limit monitoring, more reliable persistence of orchestration events, and UI refinements for settings and model selection.
The protected fork features are multi-provider runtime support, usage and limit monitoring, provider management UX, and provider-neutral orchestration reliability. Upstream syncs should preserve those unless a change explicitly replaces them with equivalent or better behavior.
Desktop builds use the T3 Code Fork name, a separate application ID, the t3code-fork://
URL scheme, and separate Electron storage. Server data defaults to ~/.t3code-fork and the
standalone server defaults to port 3873. Keep these defaults when running both apps: pointing
both builds at the same T3 database is not supported. Provider account homes remain configurable
independently of the app's own database.
Open Settings → Existing conversations, choose the Codex or Claude account that originally
ran the session, and select Find conversations. The fork reads that account's local session
files and matches official T3 titles from the default ~/.t3/userdata profile. Sessions already
managed by this fork have an Open link.
Stop the session in the other app or CLI, then choose Continue → Import and open. The fork imports saved user and assistant text into its own database and retains the original provider session ID for your next message. Importing does not send a message or modify the source T3 database. Codex resume failures are surfaced rather than silently starting a new conversation.
This supports Codex and Claude sessions with local history and an available original project folder. Discovery shows up to 200 sessions from a bounded scan; imports are limited to 32 MB and the 200 most recent text messages. T3 plans, attachments, tool records, and checkpoints are not imported, and subsequent conversation changes are not synchronized between apps. Use one app at a time for each provider session. Detected live official T3 sessions are blocked; CLI sessions require you to confirm that the other writer has stopped.
Adds full provider adapters (server managers, service layers, runtime layers) for agents that are not yet on the upstream roadmap:
| Provider | What's included |
|---|---|
| Codex CLI | App-server JSON-RPC support with usage/rate-limit monitoring |
| Claude Code | Full adapter with permission mode, thinking token limits, and SDK typings |
| Cursor | TypeScript SDK adapter + SDK model discovery + usage-dashboard tracking |
| Droid | Factory Droid SDK runtime integration |
| Fx | ACP integration through fx acp |
| Grok Build | ACP adapter with xAI protocol extensions |
| OpenCode | Adapter with hostname/port/workspace config |
| Antigravity | Official Google ACP agent with managed install and Google sign-in |
| Amp | Adapter + ampServerManager for headless Amp sessions |
| GitHub Copilot | Adapter + CLI binary resolution + text generation layer |
| Gemini CLI | Enhanced: Adapter + geminiCliServerManager with full test coverage |
| Kilo | Adapter + kiloServerManager + OpenCode-style server URL config |
| Hermes Agent | ACP chats plus an optional companion for Home, cron, handoffs, and media |
| Oh My Pi | ACP integration through the built-in omp acp mode |
| Pi | ACP integration through pi-acp, with shared model and session handling |
| Prime Agent | ACP adapter for Prime Intellect's CLI; setup |
| ACP Agent | Configurable executable and argument list for any stdio ACP implementation |
Hermes uses hermes-acp for ordinary interactive conversations. Its optional T3 companion plugin adds enrollment, proactive Home and cron delivery, handoffs, and media without replacing the standard ACP path. Oh My Pi runs its native ACP server through omp acp, while Pi stays on the shared transport through pi-acp.
In Settings → Providers, add an ACP Agent instance, enter its executable, and put one command argument on each line. Credentials and model configuration stay agent-owned; instance environment variables are inherited by the ACP process. This keeps T3 on the standard protocol instead of adding a transport fork for every compatible agent.
Real OpenRouter turns using dots-studio/dots-3-note-preview:free are covered by the live ACP
harness for:
| Agent | Executable | Arguments, one per line |
|---|---|---|
| Goose | goose |
acp |
| OpenCode | opencode |
acp |
| Qwen Code | qwen |
--acp--experimental-skills |
| fast-agent | fast-agent-acp |
Configure the model with its CLI or config |
| Docker Agent | docker-agent |
serveacp/path/to/agent.yaml |
Hermes, Oh My Pi, and Pi remain available as branded presets because Hermes has companion capabilities and the two Pi-family agents have distinct install and launch paths. For Pi models whose OpenRouter metadata advertises maximum output equal to the entire context window, install the T3 Pi compatibility extension. It omits the unsafe request field rather than imposing a replacement token cap.
Kimi CLI and Cline can launch over ACP, but their current ACP servers require their own account
authentication before session/new, even when an OpenRouter key and custom model are configured.
They can still be added through ACP Agent after completing that vendor login, but OpenRouter alone
is not sufficient in the versions tested.
- Normalized Provider Kinds: Migration added to handle legacy provider kind naming consistently.
- Improved Event Store: Robust persistence layer for orchestration events with better error handling.
- Session Management: refined
ProviderSessionDirectoryfor better tracking of active sessions.
| Feature | Description |
|---|---|
| Settings page | Dedicated route (/settings) for theme, accent color, and custom model slug configuration |
| Accent color system | Preset palette with contrast-safe terminal color injection across the entire UI |
| Theme support | Light / dark / system modes with transition suppression |
| Command palette | Cmd+K / Ctrl+K palette for quick actions, script running, and thread navigation |
| Sidebar search | Normalized thread title search with instant filtering |
| Plan sidebar | Dedicated panel for reviewing, downloading, or saving proposed agent plans |
| Terminal drawer | Theme-aware integrated terminal with accent color styling |
| Usage monitoring | Context window meter, token usage events, and account rate-limit banner/panel visibility |
Run the interactive installer — it detects your OS, checks prerequisites (git, Node.js ≥ 24, bun ≥ 1.3.9), installs missing tools, and lets you choose between development/production and desktop/web builds:
# macOS / Linux / WSL
bash <(curl -fsSL https://raw.githubusercontent.com/aaditagrawal/t3code/main/scripts/install.sh)# Windows (Git Bash, MSYS2, or WSL)
bash <(curl -fsSL https://raw.githubusercontent.com/aaditagrawal/t3code/main/scripts/install.sh)Warning
You need at least one supported coding agent installed and authorized. See the supported agents list below. Antigravity does not require a CLI: enable it in Settings, then use Install Antigravity and Sign in with Google.
# Prerequisites: Bun >=1.3.9, Node >=24.13.1
git clone https://github.com/aaditagrawal/t3code.git
cd t3code
bun install
bun run dev- Gemini CLI
- Claude Code
- Cursor
- Droid
- Fx (
fx acp) - Grok Build
- Codex CLI (requires v0.37.0 or later)
- Copilot
- Amp
- Kilo
- OpenCode
- Google Antigravity (enable in Settings, then Install Antigravity and Sign in with Google)
- Hermes Agent (
hermes-acp; runhermes-acp --setupafter installation) - Oh My Pi (install
@oh-my-pi/pi-coding-agent; T3 Code launchesomp acp) - Pi coding agent (install it together with
pi-acp, then authenticate withpi) - Any stdio Agent Client Protocol agent through the configurable ACP Agent driver
- This project is very early in development. Expect bugs.
- Interested in contributing? See CONTRIBUTING.md.
- Special thanks to Pingdotgg for the original project and aaditagrawal for the foundational fork.