Coding agentsWorkflow automation

T3 Code

pingdotgg/t3code

Drive the coding agents already installed on your machine from your phone.

Repository
Stars
17.8k
Forks
4k
Open issues
1.4k
Language
TypeScript
Licence
MIT
Created
2026-02-08
Last push
2026-08-10
Effort to adopt

Plug in

Install and use the same day. Little to no custom code.

01

What it actually does

T3 Code is not another agent. It is a control surface for the agents you already run — Claude Code, Codex, Cursor, Grok Build, OpenCode. If they are set up on your computer, T3 Code can drive them.

The interesting part is the client story: a native iOS app, a native Android app, a web app, and an Electron desktop app. You start a long task at your desk and check on it from your phone on the train, redirecting it if it has gone sideways.

It works with your existing subscriptions rather than reselling access, so there is no second bill. The maintainers are explicit in the README that they are not selling anything — it was built because existing options (the Codex desktop app, Conductor, Claude Desktop, Cursor Glass) did not meet their bar for something performant, remote-ready, and open.

MIT licensed, from the Ping/T3 team, with an active issue queue reflecting rapid development.

02

Who it's for

  • 01

    Founders and engineers who want to supervise long agent runs away from the desk

  • 02

    Anyone already paying for Claude Code or Codex who wants better ergonomics around it

  • 03

    Teams that switch between agent tools and want one control surface

  • 04

    People who start work at a laptop and want to check it from a phone

EngineeringFoundersOperationsSaaSAny industry
03

Where it earns its keep

  • Kicking off a long refactor and monitoring progress from your phone
  • Interrupting an agent that has taken a wrong turn without going back to your desk
  • Managing several agent sessions across different tools from one interface
  • Reviewing agent output during a commute rather than at end of day
  • Getting a remote-capable setup without paying for another subscription
04

Use it, or skip it

Reach for it when

  • Your agent runs are long enough that you want to check them while away
  • You already have agent subscriptions and want better control, not more capability
  • You use more than one agent tool and switching interfaces is friction
  • Mobile access is genuinely useful to how you work

Skip it when

  • All your agent work is short and interactive at a desk
  • You only use one agent and its native interface is fine
  • You would rather not expose control of your machine to a remote surface
  • You need something stable; the issue count reflects how fast this is moving
05

10 automations

  1. 01Engineering

    Commute review window

    Queue agent work before leaving and review or redirect it from the phone app on the way home.

  2. 02Engineering

    Long-run supervision

    Start a multi-hour migration at the desk and get mobile notifications when it needs a decision.

  3. 03Operations

    Cross-tool session board

    See every running agent across Claude Code, Codex, and Cursor in one list rather than four windows.

  4. 04Founders

    Founder spot-checks

    Let a non-engineering founder see what automated work is in flight without opening a terminal.

  5. 05Engineering

    Incident redirect from anywhere

    If an agent is heading the wrong way during an incident, interrupt and redirect it from a phone.

  6. 06Operations

    Overnight batch monitoring

    Schedule work overnight and check completion status from your phone before you open the laptop.

  7. 07Engineering

    Pair-review on mobile

    Share agent output with a teammate through the web app for a quick second opinion.

  8. 08Finance

    Subscription consolidation review

    Because it works across tools, compare which agent subscription you actually use and cut the rest.

  9. 09Operations

    Approval-from-phone workflow

    Have agents pause at defined checkpoints and wait for a mobile approval before continuing.

  10. 10Sales

    Remote demo prep

    Trigger a build or data refresh from the phone before walking into a customer demo.

Want one of these running by Friday?

LimeDock builds these as real workflows inside your stack — deployed to your cloud, wired into your Slack and CRM, with the code in your repo. You pay a build fee and your own API keys, nothing else.

Book a workflow call
07

Source

Repository stats were read from the GitHub API and reflect the last time we refreshed this entry. The editorial breakdown above is LimeDock’s own analysis — we are not affiliated with pingdotgg.

https://github.com/pingdotgg/t3code