Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
I run a daily Grok Bot job that downloads a csv from my Gmail, parses it through a script to beautify it via HTML, then sends a WhatsApp from the Grok Bot computer.
I decided to use Steinberger’s Wacli.sh for this job, as the whatsapp web linked device session keeps failing me, (i have to keep signing in back to whatsapp web) and after 3 days i realized its no longer reliable.
See photos
Grok bot Generated below
After an automatic computer refresh, the WhatsApp linked-device session is gone. ~/.local/state/wacli comes back empty, so the bot cannot send until I re-pair on my phone.
A daily bot that lives in the cloud should not need me in the chat every time the computer updates. Already filed this through in-app feedback.
Steps to Reproduce
Shared setup: a Grok Bot computer with a daily job that needs a linked WhatsApp session. After an automatic computer refresh (or Settings → Updates → Update Grok Bot’s Computer), check whether that session is still valid.
A. WhatsApp / wacli (this is the one that failed for me)
On the Grok Bot computer, pair WhatsApp with wacli (wacli auth --phone, then link from the phone: Linked devices → Link with phone number).
Confirm wacli auth status is authenticated. Session files live at ~/.local/state/wacli (session.db, wacli.db).
Send a test message with wacli so you know the session works.
Wait for an automatic computer refresh, or run Update Grok Bot’s Computer.
After the computer is back, run wacli auth status again and look at ~/.local/state/wacli.
Expected: still authenticated, same session files.
Actual: store is empty / recreated, status is “Not authenticated.” Project files and git on the same computer are still there. I then have to re-pair from my phone before any send works.
Last time I saw this: 20 Aug 2026, about 11:52am MYT.
B. WhatsApp Web (same bug class, not yet watched through a refresh)
On the Grok Bot computer, open Chrome and pair WhatsApp Web (web.whatsapp.com → QR from the phone).
Confirm the web session can send a message.
Trigger the same computer refresh / Update Grok Bot’s Computer.
Open WhatsApp Web again in that Chrome profile.
Expected: still logged in (Chrome’s Google login did survive the same refresh).
Actual: unknown on my machine — I did not open WhatsApp Web after the wipe. If this also drops, it is the same linked-device session loss. If it stays logged in, the wipe is specific to ~/.local/state (wacli) and not the Chrome profile.
Expected Behavior
What is supposed to “just work” is that , grok bots whatsapp linked device persists day to day, so that I can just unsubscribe from chatgpt for their automations and i dont have to keep my PC on everyday.
Operating System
Linux
Version Information
Version: 0.23.0
Release Track: stable
OS: win32
Additional Information
this is about grokbot specifically, not cursor
I am happy to share more details about my automation if it helps the bug team,
Does this stop you from using Cursor
Yes - Cursor is unusable