T3 Code Introduces Agent Harness Control Surface for Multiple AI Providers

T3 Code has emerged as a new software project described as an "agent harness control surface," designed to let users manage local AI coding agents across mobile, web, and desktop environments. According to the repository details, the tool interfaces with existing machine subscriptions including Claude Code, Codex, Cursor, Grok Build, OpenCode, Google Antigravity, and fx.

The developers state they created the project to achieve a high-performance, remote-ready, and open editor experience inspired by existing tools. The software is currently in an early development stage, with the maintainers explicitly warning users to expect bugs and noting that large feature contributions are not being accepted at this time.

Core Architecture and Supported Platforms

• Multi-Platform Access: Includes mobile applications for iOS and Android, a web app, and an Electron-based desktop app.
• Provider Integration: Connects to pre-configured local setups for Codex, Claude, Cursor, Grok Build, OpenCode, Antigravity, and fx.
• Open Access: Built to be forkable if users wish to modify or build their own customized editors.

Getting Started and Installation

• Temporary Run: Users can try the tool without a permanent installation by executing `npx t3@latest`.
• Server Setup: Running the `t3` command starts the local server and web application, while `t3 service install` manages background execution.
• Desktop and Package Managers: Desktop application builds are available via GitHub Releases, along with AUR packaging and nixpkgs support.
• Provider Authentication: Each integrated service requires individual CLI installation and login authentication prior to use, such as running `codex login` or `claude auth login`.

Verification and Practical Implications

Because the project is documented as very early stage, users should anticipate potential instability and verify instructions directly against the official GitHub repository (`pingdotgg/t3code`). The repository houses the primary documentation under the `docs/` directory, internal architecture notes, and contribution guidelines for minor fixes.