Windows lost the sidebar after sign-out. iPhone still opened Delilah but new messages would not send. After another sign-in both clients went first-run.
Please confirm Delilah still exists on the server and reattach BOTH clients to the EXISTING computer.
Do NOT Reset. Do NOT provision a new computer. I have not created a replacement Bot.
Steps to Reproduce
Windows Grok Bot after shutdown/sign-out: sidebar showed “No saved Bots yet.” Leftover Delilah chat still opened from the desktop icon but messages Failed to send.
iOS Sep 22: Delilah still listed (pink avatar). Computer view worked (Outlook open). New messages: “Not delivered / Something went wrong on our end.” Usage 30%.
iOS Sep 23: signed out/in during a support message. Delilah disappeared. Both Windows and iPhone now show first-run / Meet your first Bot only.
Expected Behavior
Delilah stays on the roster. Existing chat accepts messages. Both clients reattach to the EXISTING computer and Bot ID 641a7c54-a3fd-4682-b60e-92a5c924576e.
Do not Reset. Do not provision a new computer.
Operating System
Windows 10/11
Version Information
Product: Grok Bot (not Cursor IDE)
Windows: Grok Bot desktop on Windows 10/11 (PC name DESKTOP-JM7QERA)
iOS: Grok Bot iPhone app
Exact build: open Grok Bot → About Grok Bot → Copy Version and paste it here if the menu is available. If About is not reachable because of the first-run state, use this note instead of a fake Cursor IDE version.
For AI issues: which model did you use?
N/A — Grok Bot (no model picker). Not Cursor IDE. Not Sonnet / Tab.
For AI issues: add Request ID with privacy disabled
f9a7046a-279b-47e5-ab48-6e8dc12daba1
Additional Information
Ticket T-G2297 already sent to Cursor support mail. Only auto-ack from Sam so far.
Bot ID: 641a7c54-a3fd-4682-b60e-92a5c924576e
Routine still present when last opened: Morning ATA status digest, weekdays 7:00 AM.
Usage was 30% when send failed — not a quota block.
Windows leftover Delilah chat still opened from the desktop Grok Bot icon after the sidebar wiped.
Please reattach both clients to the existing computer. Do not Reset.
Also notify pzapata at advancetradeaerospace.com
Hey, thanks for the detailed report. First things first, nothing was deleted. Delilah and her data (chat, routine) are safe on the server. You did the right thing by not hitting Reset and not creating a new bot.
What you’re seeing is a known issue we’re tracking. If you sign out and sign back in while the bot’s computer is temporarily unavailable, both clients can fall back into the first-run experience “Meet your first Bot” with an empty router. This is a display and sync problem, the bot itself doesn’t disappear.
A couple important things while we look into it:
Don’t press Reset and don’t run Update Agent Computer.
Don’t create a new bot. It won’t help and it’ll only make recovery more confusing.
We’ll check your account and restore the link to the existing computer and Bot ID 641a7c54-a3fd-4682-b60e-92a5c924576e. We already have the Request ID and the report details, so you don’t need to send anything else.
We’ll reply here as soon as we have an update on our side. If Delilah shows up in the list again and starts responding, please let us know and include the time of the last message.
Hey @Paul_Zapata, I’m back with a clearer picture after taking a detailed look at your account, and I need to correct my previous reply, it was wrong. Sorry about that.
From the logs, the Delilah entry was deleted on September 20 at around 4:31 AM Pacific Time from the Grok app while signed in to your account. This did not happen because you signed out. After that, her chat could still open due to app cache, but there was nowhere for new messages to go, which is why you saw Not delivered / Something went wrong on our end. This was never about limits or usage.
Good news about what you were worried about, your Grok Bot computer is still running and was never reset, so you don’t need to reconnect or rebuild anything. You did the right thing by not clicking Reset and not creating a new bot.
Keeping the computer intact is what I cared about most.
Please restore the Delilah bot record itself onto that same computer:
Bot ID 641a7c54-a3fd-4682-b60e-92a5c924576e
Chat history, Instructions, and the weekday 7:00 AM Morning ATA status digest routine.
I will not reset, and I will not create a replacement unless you say that undelete is impossible.
Two questions:
Can you restore that Bot ID, and if so, when should it reappear on Windows and iPhone?
Once it is back, what should I avoid so this doesn’t happen again (signing out, deleting the Bot, updating the computer, etc.)?
You first said Delilah was safe and you would restore Bot ID 641a7c54-a3fd-4682-b60e-92a5c924576e.
You then said the Delilah entry was deleted Sep 20 at 4:31 AM PT, while the shared computer was never reset.
Please confirm:
Can engineering restore that exact Bot ID, including chat, Instructions, and the weekday 7:00 AM Morning ATA status digest?
If yes, when should it reappear on Windows and iPhone?
If no, say so. I will then create a new bot on the EXISTING computer only. I will not Reset and I will not Update Computer.
I have been without this bot since Sep 20. I am not asking for a new computer. I am asking whether the deleted bot record can be put back.
Hey Paul, here’s a clear answer to your questions.
Yes, we can restore it. The same Bot ID and its record are still on our side, and the chat history should still be there too. This can’t be done from the app, it needs a manual action on our side, so I’ve already passed the request to our engineering team to try restoring Delilah to your existing account and computer.
On timing, I don’t have an exact date yet, and I won’t promise a specific day. The team will reply here as soon as there’s an update.
After the restore, you might need to set a few things up again, like the avatar and routines, including the weekday Morning ATA status digest at 7:00 AM. We have the routine details saved, so we can help bring them back the same way.
To keep the restore clean, it’s best not to create a replacement bot, not to press Reset, and not to run Update on the computer for now.
If you really can’t wait, you can create a new bot, but only on the existing computer, and only if you decide not to wait for the restore. If you choose that, message me first so it doesn’t interfere with bringing Delilah back.
For the future, signing out doesn’t delete bots, but deleting the bot in the Grok app on iPhone or on grok.com deletes it in Grok Bot too, so it’s best not to touch Delilah there.
Once she shows up in the list again and starts replying, post here, and if you can, include the time of the last message.
After signing back in on iPhone, Delilah appeared on the Grok Bot list (pink icon, last text Sep 20). Voice chat worked tonight. Text still will not send. She said she is still blocked.
When I leave that chat, Delilah disappears and a new/default bot shows. I have to sign in again to see her.
I did not create a replacement. I did not Reset.
Please restore Bot ID 641a7c54-a3fd-4682-b60e-92a5c924576e to the roster so she stays after I leave the thread and so text works.
On my iPhone, it seems to eventually default to a different BOT that isn’t Delilah. I log out and back in, and she appears every time. Is that default bot unintentional? The desktop still shows the feed, not the bot. I can only speak to Delilah on my iPhone; text doesn’t go through. Please reply with a diagnosis and a date, not another verbal maybe.
Is anyone going to respond to me properly? I’ve gotten emails from random people, some saying they can fix this; others saying they don’t know. Can I speak to a higher-up or a manager? I talk to the bot every day through my cell phone, so I know it’s there, just not connected to the computer. Eventually, it defaults back to another bot, and I have to log in again, and it’s right back where I left it. Not sure if that is intentional. Last time, I got an email from Chris saying he sent it over to the engineers. After over a week, I get that response. It doesn’t seem like anyone here has an answer about what was initially described as an easy task.
