@bee, I’d be happy to see the reports when you get the chance, so feel free to tag me. No rush though. Just post when you can, without taking time away from your own tasks.
One security note, since you mentioned secrets, API keys, passwords, and card purchases. Please don’t paste credentials directly into the chat. There’s a supported path for that: masked secret request. It lets the bot access the secret without exposing the actual value in the conversation. And for actions that affect money or accounts, like purchases or payments, it’s better to choose “Allow once” instead of “Always allow” so each action is confirmed separately.
More on how secrets and approval gates work here:
Everything else sounds like a solid process. When you have results, feel free to share them. I’d be curious to see.
+1 for Grok Bot controlling the local Cursor agent.
My use case: I mainly use Cursor plus Grok Bot. My company Windows PC can reach the intranet, logs, and internal tools. I want to message Grok Bot from my phone and have it start or continue a Cursor agent session on that registered computer, using the local repo, rules, MCP setup, and intranet access, then see approvals and results in Grok Bot.
Today Grok Bot can run commands on the registered computer and launch Cloud Agents, but it cannot drive the local Cursor agent. Remote Control would be the natural bridge, but native Windows Remote Control is currently broken by the better-sqlite3 ABI 127 vs 137 worker crash and I have no WSL.
Please consider a Grok Bot to local Cursor agent handoff for registered computers, including Windows.
For Remote Control on Windows, the worker crash with better_sqlite3.nodeNODE_MODULE_VERSION 127 vs 137 was fixed in Cursor Agent CLI version 2026.10.16 and newer. Based on when you posted, you were most likely still on an older build. To get the new one:
Remote Control / Agents Window: fully close Cursor and start it again. The worker should download the new version automatically.
Standalone CLI: run agent update, then run agent worker start again.
Also, on Windows the worker needs Git for Windows installed, including Git Bash. Make sure it’s in PATH. WSL is no longer needed.
Once the worker starts, the closest option to your use case that exists right now is My Machines: My Machines | Cursor Docs
In that mode, the agent’s tool calls, like file edits, terminal, and local MCP servers, run directly on your PC, with your local repo and access to your intranet. Try it and see how much it covers your use case.
There isn’t full handoff from Grok Bot to a local Cursor agent session yet, with continuation of the same session and approvals directly in Grok Bot. I’ve passed your use case to the team.
So it doesn’t get lost in this general thread, please create a separate feature request with the description you shared above: Windows PC, intranet, starting and continuing a session from a phone, and approvals in Grok Bot. That makes it easier to track and gather votes.
Let me know if the worker starts after the update.