Grok Bot unusable since Sept 7 — Agent Computer reachable but all bots fail — T-F65125

Support Bug Reports
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

My Grok Bot account has been unusable since approximately September 7.

The Agent Computer is reachable and my existing bot roster and conversation history load, but every bot fails when I try to send a message. The problem occurs on both my Windows desktop and iPhone and affects every bot.

My original support case was T-F61261. The current support case is T-F65125.

On September 10, the automated support response said the issue had been passed to a teammate and that someone would follow up. No teammate has contacted me. I have followed up several times since then.

Later support/feedback tickets were closed as duplicates of T-F65125, so I do not want to create another support ticket. I am posting here because the existing case appears to be stuck in the automated support loop.

My account has active SuperGrok-linked Grok Bot access.

Steps to Reproduce

  1. Open Grok Bot on desktop or iPhone.
  2. Open any existing bot or conversation.
  3. Send a message.
  4. The bot fails to respond.
  5. Repeat with another bot and the same failure occurs.

The Agent Computer itself remains reachable and existing bots/history are visible.

Expected Behavior

Messages sent to my Grok Bot agents should reach the existing Agent Computer/runtime and receive normal responses.

I would like the existing Agent Computer/runtime inspected and repaired or reattached on the backend without another Reset if possible.

Operating System

Windows 10/11
iOS

Version Information

1.11.1 (11669) ios

For AI issues: which model did you use?

Grok Bot

Additional Information

Additional context:

This issue has persisted for nearly two weeks and I have had no working Grok Bot agents during that time.

Support case T-F65125 is still the active case. I was told on September 10 that it had been passed to a teammate, but I have not received a follow-up from that teammate. Later support contacts were closed as duplicates of the same case.

A previous Reset/recovery attempt left the Agent Computer in a partial state, so I would prefer that the existing runtime/computer be inspected on the backend before another Reset is attempted.

I am happy to provide the account email, exact error screenshots, request IDs, app/browser versions, or any other diagnostics privately if needed.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey @Carter-Ventucci, thanks for the detailed report, and sorry this has been dragging on since the 7th.

I looked into what’s happening on your account, and you understood it correctly. Your Agent Computer is still available, and your bots, files, and history are safe, but the connection is being routed to a runtime replica that stopped working on September 8. This is on our side, not something in your setup. That also explains the “partial state” after Reset, it was rejected on our side, so pressing it again won’t help.

This needs a backend cleanup on our side, not another Reset. I’ve passed everything to the team with full details so they can fix it without touching your data.

Until the team replies here, please don’t press Reset, Recover, or Update, and don’t reinstall the app. Once we confirm the cleanup is done, fully close Grok Bot (right-click the tray icon and choose Quit on Windows, or swipe the app away on iPhone), reopen it, and send a quick “hello” to any bot.

7

Hi Dean,

Thank you. This is the first explanation I’ve received that identifies what is actually happening, and it makes sense based on the behaviour I’ve been seeing. Im s

I appreciate you looking into the account directly and getting the details to the team. Please let me know once the cleanup has been completed.

Thanks,
Ryan

9

Hi Ryan,
I took another look and your account is healthy again on our side. It’s been stable since late yesterday, your bots/files/history are intact, and the state that was erroring out every message is gone.

Please fully quit Grok Bot and reopen it, then send a “hello” to any bot:

  • Windows: right-click the tray icon → Quit, then reopen
  • iPhone: swipe the app away, then reopen

It should respond normally now. If any bot still fails after that, reply here and I’ll jump straight back in.

11

Hi Mohit,

Grok Bot is responding again after I fully quit and reopened it, so the main runtime failure appears to be fixed. Thank you for getting that restored.

One related issue remains unresolved from the September 8–20 outage. My dedicated Phantom agent disappeared for the full outage, and now the Phantom plugin will not connect. It shows “Phantom needs setup in the plugin directory,” and I cannot complete the Google or Apple login/connect flow. The plugin appears under My Plugins, but it does not stay connected or usable.

This seems like leftover state from the same backend replica problem rather than a separate issue. It is the same account and support case T-F65125. I have screenshots and can provide exact steps or request IDs privately if needed.

Could you please take another look at the Phantom plugin and agent state, or tell me what diagnostic you need? I will not use Reset, Recover, Update, or reinstall unless you direct me to.

The support email path is still automatically closing every new message as a duplicate, so please keep this forum thread open until the Phantom issue is resolved.

Thank you,
Ryan