Understanding T3 Code: FAQ, Harnesses, and Remote Access

T3 Code is an open-source tool designed to integrate with various AI harnesses and provider subscriptions, functioning as a restaurant analogy where users bring their own kitchen setup. According to official project documentation, T3 Code requires an underlying harness such as the Anthropic Agent SDK or Codex App Server to operate.

Core Concepts and Harness Integration

• Definition: T3 Code itself is an interface and ecosystem wrapper, not a standalone harness.
• Brought Subscriptions: Users bring their existing subscriptions (such as Claude Code, Codex, Cursor, Grok Build, OpenCode, Google Antigravity, Pi, or Muse Code).
• Licensing: Distributed under the MIT license, with no subscription fees paid directly to T3 Code for its use.

Remote Capabilities and T3 Connect

• T3 Connect: A built-in alternative to Tailscale designed for remote connections, allowing users to drive code environments from anywhere using desktop apps, CLI tools, or mobile apps for iOS and Android.
• Machine Limits: Free accounts can connect up to three machines via T3 Connect. Linking a T3 Chat account can raise limits (up to 10 for Pro, up to 100 for Premier).
• Troubleshooting: Connection diagnostics are accessible via Settings > Environments > Machine > Details.

Provider Limits and Data Privacy

• Usage Limits: The documentation notes a reported bug involving Anthropic's Agent SDK where usage via SDK wrappers may drain 5-hour limits faster than using Claude Code directly, while weekly limits remain unaffected.
• Data Flow: Code and prompts travel directly from the user's machine to the respective provider (such as Anthropic or OpenAI) rather than through T3 servers. T3 Connect traffic utilizes a Cloudflare tunnel.
• Telemetry: Basic product usage data is collected, but telemetry can be disabled by setting `T3CODE_TELEMETRY_ENABLED=false`.

Verification and Practical Setup

To verify original setup instructions, consult the official `t3code/docs/user/faq.md` on GitHub. Users experiencing missing CLI tools should verify path configurations and ensure authentication logins are complete on the host machine running the server.