Agent control plane · Conditional recommendation

T3 Code

A fit for technical teams already using Codex, Claude Code, Cursor, Grok Build, or OpenCode that want one desktop, web, or mobile control surface for local agent sessions. It is not a standalone model subscription, security boundary, or maintenance-free cloud development environment.

Reviewed 2026-08-23Review due 2026-09-19GitHub ↗

Adoption statusConditionalBased on the evidence below

LicenseMITCheck per-directory terms

Repository snapshotActive at review★ 20,101 · Fork 4,743 · 2026-08-23
Last push 2026-08-23

Better fit

Developers using several coding agents who want one view of threads and projects
Teams willing to validate permission modes and remote access in a disposable worktree
Users who need controlled access to their own development host from a phone or another device

Think twice

Users expecting bundled model usage, replacement provider accounts, or hidden underlying CLI costs
Teams unable to manage Node, provider CLIs, session credentials, network exposure, and version sync

Adoption and exit evidence

A repository is a dependency decision, not only a download.

Compatibility

Official documentation lists Codex, Claude, Cursor, Grok Build, and OpenCode and requires the matching CLI to be installed and authenticated on the server machine. Desktop packages cover macOS, Windows, and Arch Linux; background-service documentation currently covers Linux and macOS.

Installation

The smallest trial runs npx t3@latest on a compatible Node.js version. Desktop builds are available through GitHub Releases, Homebrew, winget, or AUR. Enable one authenticated provider first and begin in Supervised permission mode.

Removal

Stop the temporary process or uninstall the desktop app. If a background service was installed, use the documented service uninstall command. Then revoke remote sessions in t3 auth, remove any Tailscale Serve mapping, and inspect ~/.t3, provider shadow homes, and startup entries before deleting local data.

Permissions

Permission modes are per thread, while the documentation says new threads may default to Full access. A paired device can create sessions, and the backend retains project files, Git state, terminals, and provider sessions. Treat pairing links, tokens, browser history, and network binding as sensitive credentials.

Maintenance

GitHub API showed the repository unarchived with 20,101 stars, 4,743 forks, and a same-day push on August 23, 2026. The README also says the project is very early and users should expect bugs, so this profile uses a 30-day review.

License boundary

The main repository is MIT. Codex, Claude, Cursor, Grok Build, OpenCode, Tailscale, mobile stores, and package managers retain their own terms; MIT does not cover model charges, provider data handling, or third-party services.

Primary risk

What can go wrong after installation?

The main risk is a wider control-plane blast radius: default Full access, remote pairing, terminal execution, multiple provider credentials, and real repositories meet in one surface. Reduce permissions, constrain network reachability, use a disposable worktree, and prove session revocation and service removal first.

Evidence status

The Product Hunt August 2026 Development discovery signal, official README, installation, permission modes, remote access, updating, background service, MIT license, and public GitHub metadata were reviewed. ToolPickly has not completed a cross-device sandbox test with real provider accounts or audited every dependency and mobile client.

Run this controlled pilot

Do not use production credentials or sensitive customer data.

01
Connect one test provider in a secret-free disposable worktree and select Supervised
02
Record local ports, created files, terminal commands, Git changes, and provider-session access
03
Pair a second device only through a tailnet, then revoke the token and established session
04
Remove the background service and clients, then verify startup entries, ports, sessions, and the test repository are clean

Open the complete adoption checklist →

Alternatives by decision

Provider 原生客户端

For one agent, its native CLI or desktop client usually has a smaller permission surface and shorter failure chain.

Git Worktree + 终端复用器

Better for local parallel work when mobile remote control is unnecessary.

Superpowers

Better when development method and quality gates matter more than controlling multiple agents.

Official sources and disclosure

Stars are a dated attention signal. They do not determine the verdict. ToolPickly reviewed public repository documentation and clearly identifies what has not been sandbox-tested.

Report a project change or correction →