Paseo vs T3 Code
Paseo and T3 Code both put a desktop, web and mobile interface over coding agents that run on your own machine, with git worktrees for isolation. Paseo is a daemon with workspaces, an MCP server and tools that let agents spawn other agents. T3 Code is organized as threads, can fan one prompt out to several models, and is MIT-licensed.
Facts side by side
| Fact | Paseo | T3 Code |
|---|---|---|
| Type | Orchestrator | Orchestrator |
| Languages / SDKs | TypeScript | TypeScript |
| License | unknown | MIT |
| Pricing model | Open core | Open source, free |
| Orchestration pattern | Supervisor | Other |
| GitHub stars | 19,066 (as of 2026-09-30) | 23,963 (as of 2026-09-30) |
| GitHub forks | 2,211 | 6,266 |
| Last push | 2026-09-30 | 2026-09-30 |
| Latest release | v0.10.2 | v0.0.44 |
| Repository | getpaseo/paseo | pingdotgg/t3code |
| Website | paseo.sh | t3.codes |
| Documentation | paseo.sh | github.com |
| Last verified | 2026-09-30 | 2026-09-30 |
| MCP support | Yes (checked 2026-09-30) | Yes (checked 2026-09-30) |
| A2A support | Unknown (checked 2026-09-30) | Unknown (checked 2026-09-30) |
| AG-UI support | Unknown (checked 2026-09-30) | Unknown (checked 2026-09-30) |
| Install verified | 2026-09-30 | Not yet |
Choose Paseo if
- You want agents to orchestrate other agents: with Paseo tools enabled, an agent can create workspaces and spawn workers on any configured provider.
- You want a Docker image for the daemon, a TypeScript SDK or CLI scripting.
- You care about the README's statement of no telemetry, tracking or forced log-in.
Choose T3 Code if
- You want to compare models: shift-select several models to fan one prompt into several threads, each in its own worktree.
- You want per-thread permission modes and pull request review and merge in the app.
- You want a plain MIT license and accept 0.0.x releases.
Migration notes
Both drive the agent CLIs installed on the host, so provider logins carry over. Paseo keeps worktrees under $PASEO_HOME/worktrees/; T3 Code keeps state under ~/.t3/userdata and creates worktrees per thread. Push or merge open branches before switching. Defaults to review: T3 Code's initial permission mode is Full access and it sends product usage events to PostHog unless telemetry is disabled; Paseo's agent-spawning tools are off by default and its plugins run with access to the daemon machine. License: T3 Code is MIT; Paseo's LICENSE file is Apache-2.0 text, though GitHub reports no license. Paseo also offers a managed Hub with Free and Pro plans.
FAQ
Can I control agents from my phone with both?
Yes. Both records list iOS and Android clients that act as remote controls for a machine that holds the code.
Which agents are supported?
Both list Claude Code, Codex and OpenCode. Paseo's supported-providers page also lists Hermes Agent and other ACP agents.
Does either have a coordinator agent?
Paseo can, when its tools are enabled for an agent. T3 Code's record notes that parallel work is manual and no planner that assigns work between agents is documented.