Skip to content

Grok Bot app 1.1.0: listAgents fails with 404 'The request could not be routed' via EnsureSandBox route #168

Open

Description

@ricklesgibson

Setup: macOS (Apple silicon), Grok Bot desktop app 1.1.0 (signed in, running), gbot 0.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

Happy to run more diagnostics.

Activity

  1. ricklesgibson commented on Nov 16, 2026

    @ricklesgibson
    Author

    Update: local hotfix resolved the listAgents routing 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:

    • Bot listing returned HTTP 200.
    • Bot lookup by name returned HTTP 200.
    • All four bundles passed syntax checks.
    • 32 routing-parser tests passed.

    Caveats:

    • This is a local hotfix, not an upstream fix or release, and not a guarantee of stability.
    • Repeatability testing is not yet confirmed.
    • Thread retrieval and live MCP operation are unverified.
    • Not yet validated in a separate environment.
    • No messages were sent during testing; credentials, billing and remote-access policy were unchanged.
    • Rollback restores the backed-up originals; reinstalling the CLI may overwrite the hotfix.

    Leaving this open until there is a durable upstream fix.

  2. tobyatgithub commented on Nov 17, 2026

    @tobyatgithub

    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)
    send 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) 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.

  3. bo-lora commented on Nov 22, 2026

    @bo-lora

    Same failure here on a newer app version.

    Setup: macOS (Apple silicon), Grok Bot desktop app 1.2.3 (signed in, running), gbot 0.12.5 via npm install --global grok-bot-cli, Node v25.2.1.

    Symptom:

    $ 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions