You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Grok Bot app 1.1.0: listAgents fails with 404 'The request could not be routed' via EnsureSandBox route #168
Setup: macOS (Apple silicon), Grok Bot desktop app 1.1.0 (signed in, running), gbot0.12.5 via npm install --global grok-bot-cli, Node v24.21.0.
Symptom: every read fails, e.g.
$ gbot bots list
[render-failed] listAgents failed: 404 The request could not be routed
Retrying over ~30s (app open the whole time) gives the same result.
gbot doctor:
resolved: (none)
gateway auth: present
Grok Bot app session: not found
Grok Bot active account credentials: present
Request trace (a --import hook that wraps fetch and logs only method/host/path/status; pod hostname redacted):
POST api2.cursor.sh/aiserver.v1.GrokBotService/EnsureSandBox -> 200
POST <pod>.us10.cursorvm.com/api/listAgents -> 404 ("The request could not be routed")
Observations
App 1.1.0 writes no gateway-descriptor.json; its state is now base32-named blobs under ~/Library/Application Support/Grok Bot/sand-client-persistence/, so the CLI takes the EnsureSandBox fallback.
EnsureSandBox succeeds and returns a *.cursorvm.com route, but that route 404s on /api/listAgents.
gatewayCall only refreshes the route on 417 from anyrun-proxy, so a 404 could not be routed is never retried with a fresh route.
Confirmed the same on my end (macOS, app 1.1.0, same trace: EnsureSandBox 200 → /api/listAgents on the cursorvm pod 404s). I dug into the 1.1.0 asar and there's a cleaner way out than fixing the pod routing: the desktop app itself no longer uses the pod /api/* REST surface at all. In 1.1.0 everything goes through connect RPCs straight to api2.cursor.sh, same route #166 uses for send.
Where to look: dist/electron-main/proto.cjs in the app bundle contains the full connect-es service definitions — GrokBotService alone has 140+ methods. The requests work with plain JSON bodies (Content-Type: application/json + Connect-Protocol-Version: 1, Bearer token from the usual Cursor credentials, current app version in x-client-version).
The three RPCs that cover the CLI's core surface (all verified 200 end-to-end against 1.1.0):
CLI need
RPC
Request
bots list
GrokBotService/ListGrokBotAgents
{}
thread read
GrokBotService/ListGrokBotTranscriptEntries
{agentId, limit, beforeSeq} — newest-first, beforeSeq cursor paging; each entry's body is base64-encoded JSON (kind: "message" = user, kind: "send-message" = bot reply)
So reads can ride the same backend as #166's send fix instead of resurrecting the pod route — that also sidesteps the 404-never-refreshes-route problem in gatewayCall, since there's no pod route to refresh.
Bonus endpoints that may be useful later: WatchGrokBotTranscripts (streaming alternative to polling) and SearchGrokBotTranscripts.
Heads-up: GetGrokBotSendStatus exists too, so send receipts can be checked directly instead of grepping the transcript.
I've been running a small standalone wrapper on these three RPCs for a few days now — reads and sends both stable. Happy to help port this into the CLI if there's interest.
$ gbot bots list --gateway
[render-failed] listAgents failed: 404 The request could not be routed
gbot doctor:
resolved: (none)
gateway auth: present
Grok Bot app session: not found
Grok Bot active account credentials: present
Request trace (a --import hook that wraps fetch and logs only method/host/path/status; pod hostname redacted):
POST api2.cursor.sh/aiserver.v1.GrokBotService/EnsureSandBox -> 200
POST <pod>.us9.cursorvm.com/api/listAgents -> 404
App 1.2.3 writes no gateway-descriptor.json, so the CLI takes the EnsureSandBox route, as in the original report. On 0.12.4 the CLI could not sign in at all on this app version; 0.12.5 gets past sign-in and stops at the 404.
#169 looks like the fix for this and #166 for the send failure that follows it. Is a release with those two planned? Happy to test a prerelease.
Activity
ricklesgibson commentedon Nov 16, 2026
Update: local hotfix resolved the
listAgentsrouting 404 (Grok Bot app 1.1.0, gbot 0.12.5)The CLI was dropping the gateway port token that routing requires. Preserving that token restored bot listing and lookup in the tested environment.
The hotfix patches four installed CLI/MCP bundles, preserving existing patches and keeping exact backups of the originals.
Reported verification:
Caveats:
Leaving this open until there is a durable upstream fix.
tobyatgithub commentedon Nov 17, 2026
Confirmed the same on my end (macOS, app 1.1.0, same trace: EnsureSandBox 200 →
/api/listAgentson the cursorvm pod 404s). I dug into the 1.1.0 asar and there's a cleaner way out than fixing the pod routing: the desktop app itself no longer uses the pod/api/*REST surface at all. In 1.1.0 everything goes through connect RPCs straight toapi2.cursor.sh, same route #166 uses for send.Where to look:
dist/electron-main/proto.cjsin the app bundle contains the full connect-es service definitions —GrokBotServicealone has 140+ methods. The requests work with plain JSON bodies (Content-Type: application/json+Connect-Protocol-Version: 1, Bearer token from the usual Cursor credentials, current app version inx-client-version).The three RPCs that cover the CLI's core surface (all verified 200 end-to-end against 1.1.0):
GrokBotService/ListGrokBotAgents{}GrokBotService/ListGrokBotTranscriptEntries{agentId, limit, beforeSeq}— newest-first,beforeSeqcursor paging; each entry'sbodyis base64-encoded JSON (kind: "message"= user,kind: "send-message"= bot reply)GrokBotService/SendGrokBotUserMessage{agentId, messageId, text, sentAtMs}—dispatched: true= accepted (what #166 already implements)So reads can ride the same backend as #166's send fix instead of resurrecting the pod route — that also sidesteps the 404-never-refreshes-route problem in
gatewayCall, since there's no pod route to refresh.Bonus endpoints that may be useful later:
WatchGrokBotTranscripts(streaming alternative to polling) andSearchGrokBotTranscripts.Heads-up:
GetGrokBotSendStatusexists too, so send receipts can be checked directly instead of grepping the transcript.I've been running a small standalone wrapper on these three RPCs for a few days now — reads and sends both stable. Happy to help port this into the CLI if there's interest.
bo-lora commentedon Nov 22, 2026
Same failure here on a newer app version.
Setup: macOS (Apple silicon), Grok Bot desktop app 1.2.3 (signed in, running),
gbot0.12.5 vianpm install --global grok-bot-cli, Node v25.2.1.Symptom:
gbot doctor:Request trace (a
--importhook that wrapsfetchand logs only method/host/path/status; pod hostname redacted):App 1.2.3 writes no
gateway-descriptor.json, so the CLI takes theEnsureSandBoxroute, as in the original report. On 0.12.4 the CLI could not sign in at all on this app version; 0.12.5 gets past sign-in and stops at the 404.#169 looks like the fix for this and #166 for the send failure that follows it. Is a release with those two planned? Happy to test a prerelease.