Repository navigation
Manage Cursor, Codex, and Claude cloud sessions from inside T3 #15644
Description
Activity
+1, this would be a huge unlock — especially on Cursor
+1. My use case: I move my long work (eval suites, multi-hour builds) from local machines to Claude cloud sessions, and I want T3 to stay the one place where I see and steer all of it.
The Claude CLI already gives most of the surface a first version needs:
- Start:
claude --cloud "<task>"makes a cloud session for the current repo and prints itsclaude.ai/code/<id>URL. - Steer:
claude -p "<message>" --cloud <session-id>queues a message into a running session (--output-format jsongives{ok, session_id, url}). - Pull back:
claude --teleport <session-id>checks out the session's branch and loads its history locally. That could map to "continue this cloud session as a local T3 thread".
Docs: https://code.claude.com/docs/en/claude-code-on-the-web
A small first step: an "open in cloud" action on a Claude thread that runs
--cloud, then shows the session link and status in the thread. Cloud sessions use the same plan limits as local Claude Code and have no VM charge, so the cost is the same for users.- Start:
Related to #15516 (isolated workers), but this is the hosted coding-agent side, not a generic sandbox.
I want T3 to start, list, steer, and stop cloud sessions for Cursor, Codex, and Claude without leaving T3. The parent thread stays the control plane. Each cloud session shows up as work I can follow, the same way a local provider thread does.
What I want:
This is not a request for T3 to own Daytona, Docker, or E2B. That split is already in #15516. Here the compute is the vendor's own cloud agent.