T3 Code controls the agents on your machine. intentic gives each agent a machine.
Of everything on this page, this shares the most premises: your subscription, your hardware, MIT source, and a real answer for your phone. What is left over is the layer under the agent.
“The open-source control plane for coding agents.” Orchestrate Claude Code, Codex, OpenCode, Cursor and Grok from one surface. Bring your own subscription. Fork the whole thing.
T3 Code drives harnesses that are already installed and signed in on one computer, from a desktop app, a web app and native iOS and Android apps that all talk to the server running there. It is MIT, it is free, and it asks for nothing you are not already paying for.
intentic agrees with all of that and then changes what an agent inherits. Instead of your machine as it stands, it gets a container built from an image you approve, capabilities that hand it your systems, and events that can start it while you are asleep.
So the question is not which surface is nicer. It is whether the work you want done needs an environment you can change.
Where we agree
Bring your own subscription: nothing resold, metered or capped by either of us. The harness is a choice rather than a lock-in, and switching it mid-thread is ordinary. Both engines are MIT, so you can read what wraps your agent before you trust it. And an agent you started at your desk should be answerable from your pocket.
Where they differ
What the agent inherits
T3 Code launches the CLIs installed on the computer running its server, so an agent's reach is your reach: your PATH, your logins, your installed clients. In intentic the agent's machine is an image, extended by an overlay Dockerfile you approve, and two agents on one host can have entirely different toolchains.
Systems, not just files
Capabilities wire a sandbox to GitHub, PostgreSQL, Sentry, Stripe, Discord, SSH and MCP servers, each keeping its credential inside. That is the difference between an agent that hands you a patch and one that can close the loop itself.
Two ways to be reachable
T3 Code pairs a device with a token over your LAN or your own tailnet, which depends on nobody. An intentic sandbox dials a private tunnel outward instead, so there is no network to arrange and the host can sit somewhere you have no route to.
Isolation that is not a per-thread decision
In T3 Code a thread takes a branch, and a worktree when you ask for one. Here every conversation gets its own worktree by construction, and landing replays its delta onto your tree as ordinary git changes you can stage, amend or revert.
Running when nobody is watching
Automations start a fresh session on a schedule, a push, an alert, a payment, an email or a chat message, gated by a guard command you write. A control plane runs the threads you open.
Head to head
| Dimension | intentic | T3 Code |
|---|---|---|
| What it is | the machine an agent works on | a control surface for the agents on your machine |
| Where the agent runs | a Docker sandbox on hardware you own | your machine, against your local checkout |
| Host operating system | macOS, Linux, Windows via WSL2 | macOS, Windows and Linux |
| Harnesses | Claude Code, Codex, Grok, Kimi Code or Google, plus any ACP agent | Claude Code, Codex, Cursor, Grok and OpenCode |
| On a phone | the workspace in a mobile browser | ▸ native iOS and Android apps |
| What you can change about the environment | the image, the capabilities, the context loaded each turn | your machine, as it already is |
| Where credentials live | inside the sandbox, injected per turn | your shell, one login per harness |
| How you reach it from elsewhere | a private tunnel the sandbox dials out; nothing inbound is opened | a pairing token over your LAN or your own tailnet |
| Isolation | one git worktree per conversation, always | a branch per thread; a worktree when you ask |
| Starts on an event | automations: cron, webhook, push, alert, email, chat | you start each thread |
| Setup | Docker, a Google account, one pasted command | ▸ npx t3, or one desktop app |
| Licence | MIT sandbox and CLI; the hosted platform is closed | ▸ MIT throughout |
Pick T3 Code when
Everything your agents need is already installed and signed in on the computer you use, you want native iOS and Android rather than a browser tab, and you would rather run one MIT app — no container runtime, no account, no platform anywhere — than configure an environment.
Every claim above is checkable on t3.codes and in this repo. Where we have it wrong, open an issue and it gets fixed in the next build.