sendPrompt failed: 502 A Sand box session is not permitted on this endpoint. #165

Activity

1. laschweinski commented on Nov 5, 2026

   

   laschweinski

   on Nov 5, 2026

   Author

   More actions

   gbot doctor
   resolved: (none)
   gateway auth: present
   Grok Bot app session: usable
   Grok Bot active account credentials: present
   found:
   (none)
   candidates:
2. Philipp0205 commented on Nov 5, 2026

   

   Philipp0205

   on Nov 5, 2026

   More actions

   same problem here since today...
3. b0bthcdrz commented on Nov 5, 2026

   

   b0bthcdrz

   on Nov 5, 2026

   More actions

   Same here, with some details that might help narrow it down.

   Setup: macOS, Node 24 via npx, Grok Bot desktop app 0.78.4, gbot 0.12.4 and now 0.12.5.

   Timeline

   • Earlier this week gbot send to bots worked (0.12.4, app 0.75.0).
   • The app auto-updated to 0.78.4. gbot doctor then said Grok Bot app session: present but unusable: Unsupported Grok Bot gateway descriptor version 3.
   • Upgraded to 0.12.5 (the changelog mentions descriptor v3). gbot doctor now says Grok Bot app session: usable and Grok Bot active account credentials: present.
   • Reads work (gbot thread <bot>, gbot bots list). Every send fails: sendPrompt failed: 502 A Sand box session is not permitted on this endpoint. (delivery unknown; check the thread before resending). Nothing shows up in the target's thread.

   Tried, same result

   • With CURSOR_ACCESS_TOKEN read from Cursor's state, and with it unset so the CLI uses the app's own session (also with SAND_CLIENT_VERSION unset, so it reports the installed app version).
   • Four different bots and one group as targets (one send to a bot timed out once, the rest 502).
   • --gateway.
   • Fully quitting and reopening the Grok Bot app.

   Looks server-side: the message suggests the send endpoint now rejects "sand box" (box) credentials while read calls pass. The MCP gbot_send tool is not affected by this (it just reports missing credentials).

   Is there a flag or env var to pick the non-box endpoint for sends? Happy to run any debug output that would help.
4. Philipp0205 commented on Nov 5, 2026

   

   Philipp0205

   on Nov 5, 2026

   Last edited by Philipp0205

   More actions

   I works again on my side, my agent wrote a fix :) Let me review it and create a PR.

   👍React with 👍1Reacted by AppworkZ (pdwtr)
5. crayment commented on Nov 6, 2026

   

   crayment

   on Nov 6, 2026

   More actions

   Hitting this too, on macOS.

   Setup: macOS (Apple silicon), Grok Bot desktop app 0.78.1, gbot 0.12.5 installed via npm install --global grok-bot-cli, Node v26.8.1.

   Symptoms — identical to above:

   • Reads work fine: gbot bots list and gbot thread <bot> both return correct data.
   • Every send fails: sendPrompt failed: 502 A Sand box session is not permitted on this endpoint. (delivery unknown; check the thread before resending)
   • Confirmed nothing was actually delivered — the target bot's thread has no new entry, so the "delivery unknown" resolves to "not delivered".
   • --gateway makes no difference.
   • Tried two different target bots, same result both times.

   gbot doctor:

   resolved: (none)
   gateway auth: present
   Grok Bot app session: not found
   Grok Bot active account credentials: present
   

   Note this differs slightly from the report above: mine says not found rather than usable. There is no gateway-descriptor.json anywhere under ~/Library/Application Support/Grok Bot/ on my machine, so the CLI is taking the EnsureSandBox fallback path to get a route — and that route still gets the same 502 on send while passing on reads. So the failure doesn't appear to depend on descriptor version or on which credential path resolved.

   One separate usability note: before I granted macOS Keychain access to the Grok Bot Safe Storage item, every gbot command (including bots list) hung silently and indefinitely with no output and no error — the authorization dialog isn't visible when the command runs from a non-interactive shell. A stderr line like "waiting for Keychain authorization" would have saved me a while. Happy to file that separately if it's useful.

   Looking forward to #166 landing.