Feature request for product/service
Cursor IDE
Describe the request
I’d like a lightweight way to continue an existing local agent chat from the web or phone, similar to Claude Code and Codex. The agent would keep running on my computer. Phone and web would only sync that conversation and let me send the next message. I wouldn’t need a second environment, a Cloud VM, or a separate “This PC (Remote Control)” session.
Why this would help
I already work in a normal local agent chat, with the real project open: local MCP servers, computer use, Unity, uncommitted files, and the other tools that live on this machine. Before I leave, I’d like to give that same agent more work, then send follow-ups from my phone. The conversation I started at my desk would just continue.
Putting this into a separate Remote Control / cloud-style workspace is harder to use in practice:
- I spend time on “Setting up environment” instead of talking to the agent I already have.
- I have to switch between the local chat and a second session, and context doesn’t carry over cleanly.
- A split workspace also loses some connectivity. Local MCP, computer control, and other machine-specific tools work well in the normal local agent. They tend to be weaker or missing once the work is handed off somewhere else.
If possible, I’d love for web and mobile to attach to the existing local chat: sync messages, send the next instruction, and show the reply. No extra checkout, no extra worker environment, and no session fork.
Related requests
This is in the same direction as the Claude Code / Codex-style local relay others have asked for:
I understand from staff replies that today’s Remote Control creates a cloud-side representation plus a local worker, which is why “This PC” and “This PC (Remote Control)” are different sessions. I’m hoping for a thinner option: a message pipe into the chat that is already running, rather than a new session that has to recreate the machine.
Current Remote Control (brief note)
This is a feature request, not a bug report. I’ll only mention that the current Remote Control handoff can be a bit heavy and unreliable on Windows — it sometimes sits on setup environment / waiting for a self-hosted worker. That’s one reason a lightweight attach-to-local-chat design would be really helpful.
Thank you for considering this. I’d be grateful to hear whether a thin relay on top of the existing local agent is something the team would consider.
Operating System (if it applies)
Windows 10/11