T3 Code explained: the client controls work on another machine
T3 Code explained: the client controls work on another machine
Learn the environment boundary before opening a coding agent from a phone or browser
What you will learn
- Find where execution happens
- Understand the agent dependency
- Read the scope of this series
Before you start
- A disposable project on an environment host
- One authenticated supported provider
Turn a disposable trial into evidence before connecting important repositories
Key takeaways
- A remote client does not move execution to the phone.
- The hosted web app connects directly to the environment.
- T3 Code still depends on provider accounts.
Find where execution happens
T3 Code supplies web, desktop and mobile clients for coding agents installed on a host. The server environment owns the workspace, provider process, terminal, Git operations and durable state. A remote screen controls that environment rather than executing on the phone.
This distinction avoids a common error: a file visible in a remote thread belongs to the server machine, not to the client device. The hosted web app also connects to the chosen environment directly; it is not a proxy for a private server.
Understand the agent dependency
The pinned README supports installed and authenticated Codex, Claude, Cursor, Grok Build, OpenCode and Antigravity. T3 Code is a control surface over those providers, not a replacement model subscription.
A client can launch without an authenticated provider, but it cannot start a useful coding thread until one is configured on the environment that will run it. Choose a single provider first and confirm its account and permission mode.
Read the scope of this series
The nine chapters cover first run, remote deployment, RPC and event-log design, source entry points, cost, authorization, alternatives and a pilot. The project calls itself early and warns users to expect bugs.
This is a fixed-source review of commit `4ee6bfd`; it did not install T3 Code, connect a phone or execute an agent. Treat architecture statements as documented behavior until you test them on your host.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Identify the environment that owns files and provider credentials.
- 2
Choose one authenticated coding-agent provider.
- 3
Use a disposable project for a first remote trial.
Copy-ready example
phone / web / desktop -> authenticated RPC -> environment
environment -> provider + terminal + Git + filesFrequently asked questions
Does the web app run Codex in my browser?
No. The environment server launches the configured provider on its own machine.
Can I use T3 Code without a provider login?
You can open the app, but an agent thread needs an authenticated supported provider.
Sources
- T3 Code / README.mdSource checked 2026-10-04
- T3 Code / docs/user/install.mdSource checked 2026-10-04
- T3 Code / docs/internals/overview.mdSource checked 2026-10-04
- T3 Code / docs/internals/remote.mdSource checked 2026-10-04