T3 Code

T3 Code exposes a Node server for provider-backed coding threads. A thread is the durable conversation/workspace unit; a turn is one user-to-agent work cycle inside a thread.

Required Surface

Use server-side orchestration surfaces only:

• Use a native thread-control MCP/tool only if it dispatches to the T3 Code server RPC.
• Otherwise use the server HTTP orchestration API when the prompt or environment provides httpBaseUrl plus a bearer token, or the user explicitly authorizes issuing a token.
• If RPC access is unavailable, ask for the missing server URL, project id, or authorization.
• Require the official t3 CLI on PATH for local scripted control. If t3 is missing, stop and ask the user to install it; do not use t3code, AppImage internals, or a local t3-code source checkout.

Local Desktop Discovery

For a running local T3 Code desktop/server: