Rank #02 · Daily · AI
T3 Code: Agent-Harness Control Surface for Claude Code, Codex, Cursor & More
A remote-ready control plane for the coding agents you already authenticated—desktop, web, and phone—without locking you into a closed editor.
What it does
T3 Code (pingdotgg) calls itself an “agent harness control surface.” It does not replace your agent subscriptions; it controls agents already installed and logged in on your machine—Claude Code, Codex, Cursor (CLI / agent login), Grok Build, OpenCode, Google Antigravity, and fx—through:
- an Electron desktop app,
- a web app (app.t3.codes),
- and iOS / Android remote apps.
Install paths include curl https://t3.codes/install.sh | sh, Windows install.ps1, npx t3@latest, and packaged desktop builds (winget, Scoop, Homebrew cask, .deb, AUR, nixpkgs). t3 starts the server and local web UI; t3 service install can keep it in the background; t3 update moves to a newer release.
Provider setup (from README warnings): install and authenticate at least one of Codex (codex login), Claude Code (claude auth login), Cursor CLI (agent login), Grok Build (grok login), OpenCode (opencode auth login), Antigravity (Settings → Install / Google sign-in), or fx (fx login on the machine running the T3 server). Docs under docs/ cover remote access, permission modes, keyboard shortcuts, project settings, appearance, MCP connections to outside agents, background service setup, and multi-account notes for Codex/Claude. Site: t3.codes.
The README is blunt: the project is early, expects bugs, and is mostly not accepting large contributions yet (small fixes maybe; big features no). Vite+ / vp is used for building from source.
Who it’s for
Developers who already pay for or use multiple CLI coding agents and want one remote UI—especially from a phone or another machine—without migrating to a single proprietary desktop. Fork-friendly MIT positioning is explicit: if the product direction diverges, you should still have what you need to build your own editor surface.
Practical caveats for overseas developers: authenticate providers before first run; read permission-mode and remote-access docs before exposing the server beyond localhost; expect churn while the project is early.
Stars / language / license
~40,260 stars · TypeScript · MIT
Data verified: 2026-11-02 ~22:16 Asia/Shanghai (GitHub API get_repository + README get_file_contents)
Trending note (selection ~22:14 Asia/Shanghai): ~+3,216 stars today — largest credible daily growth on this Top10 list (archive earlier same day ~+3,094)
Category tags
AI · agent-harness · developer-tools · remote-coding · Electron · mobile · MCP
How it differs from similar projects
README inspiration list includes Codex desktop, Conductor, Claude Desktop, and Cursor Glass—none of which met the authors’ bar for performant, remote-ready, and truly open. Unlike an agentic IDE that embeds one engine, T3 Code is a multi-provider harness UI over tools you already installed. Unlike cloud IDEs, agents run on your computer; remote clients talk to your local/server process.
GitHub’s API currently shows no repository description field—rely on the README and t3.codes for positioning. The Rising narrative for overseas developers is the breakout “agent harness” UX: one control plane across clients and vendors, MIT-licensed, aggressively shipped while still early. Pairing note: memory plugins such as claude-mem advertise T3 Code install paths separately—this article does not endorse a specific stack combo beyond what each README documents.
Practical notes for overseas developers
- Treat it as a control plane, not a model host. Subscriptions and CLI auth stay with Claude/Codex/Cursor/etc.; T3 Code remotes the UI.
- Remote access is a security surface. Follow
docs/user/remote-access.mdand permission modes before pairing a phone or exposing beyond localhost. - Expect early-software edges. High star velocity (+3k-class day) can outrun polish; the README’s “expect bugs / limited contributions” disclaimer is load-bearing.
- MCP outside-agents docs matter if you want Claude Code/Codex/ChatGPT-style tools to talk to the same harness—read before inventing glue.
The Daily Rising story is less “another AI IDE” and more agent harness as product category: one MIT control surface across the coding agents developers already bought.