T3 Code control surface for AI coding agents is now synced across GitHub and GitCafe

A post that reached the Hacker News front page announces that T3 Code, a cross-platform control surface for AI coding agents, is now synced between GitHub and GitCafe. The project's repository is published under the pingdotgg account at git.cafe, and the same code is mirrored across both forges, according to the post.

What T3 Code does

According to the project's GitCafe page, T3 Code is software that runs on your machine and lets you control the AI coding agents you already have installed, rather than replacing them. It exposes that control through three clients: an iOS and Android mobile app, a web app, and an Electron-based desktop app. The documentation includes a guide on reaching your agents from a phone or another computer, so remote use is treated as a first-class scenario rather than an afterthought.

The page is direct about the business model: there isn't one. The team says it built T3 Code for its own agent-driven development workflow, took inspiration from the Codex desktop app, Conductor, Claude Desktop and Cursor Glass, and found none of them good enough. Openness is pitched as insurance — if the project ever heads in the wrong direction, users should have everything they need to fork it and build the editor they want.

Which agents it supports

T3 Code piggybacks on subscriptions you already hold instead of bundling models of its own. Six providers are supported: Codex, Claude Code, Cursor, Grok Build, OpenCode and Google Antigravity. At least one has to be installed and authenticated before T3 Code will do anything — Codex through codex login, Claude through claude auth login, Cursor's CLI through agent login, Grok Build and OpenCode through their own login commands, and Antigravity through the app's settings with a Google sign-in, no CLI required.

The documentation also covers connecting Claude Code, Codex, ChatGPT and other agents over MCP, and running multiple accounts side by side for Codex and Claude.

Installation and availability

The server side is a command-line tool. Running t3 starts the server and opens the local web app, t3 service install keeps it running in the background, and t3 update moves to a newer release. Anyone who wants a one-off trial can run npx t3@latest without installing anything.

The desktop app is distributed through GitHub Releases and the usual package managers: winget and scoop on Windows, Homebrew on macOS, a .deb package for Debian and Ubuntu, and an AUR package for Arch that the repository maintains itself.

Project maturity

The maintainers are candid that the project is at an early stage and buggy. They are also mostly closed to outside contributions for now: small fixes may be considered, but large features will not be accepted.

Documentation lives inside the repository's docs directory, with no dedicated docs site yet. Feature requests go through an Ideas discussion, support happens on Discord, and anyone building from source needs the vp command-line tool because the project is built on Vite+.

Why it matters

Two things make this worth watching. First, the tool itself: developers increasingly hold several agent subscriptions at once, each with its own desktop app or terminal workflow, and a neutral control surface that spans phone, browser and desktop — while staying forkable — is a credible answer to that fragmentation.

Second, the sync itself. Keeping the repository current on both GitHub and GitCafe means the project no longer depends on a single code host, which is a reasonable hedge at a time when many projects are thinking about platform concentration. For a project whose stated fallback is forking, having a second canonical home makes that promise easier to keep.