Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Where: Grok Bot desktop app (macOS) + Routines that target a registered machine
What happened
My MacBook Air (Johns-MacBook-Air.local) used to register as machine b3347a31-ff41-435a-acdd-4913606709eb. It now shows up as a new machine, 4535eb5c-483a-46f5-8db9-8fdd0db70fbb, and the old ID is listed as disconnected. I did not reinstall the app. It probably happened during an auto-update (0.70.2 built 2026-10-11 → 0.71.2 built 2026-10-14), but I’m not sure when the update landed.
Impact
A routine (“Apple Reminders to Todoist”) that runs osascript on this Mac by machine ID failed both of its runs on 2026-10-16 (7:46 AM and 7:43 PM ET). It only worked again after the routine was manually re-pointed to the new ID. Nothing told me the machine had changed identity.
Expected
- An update keeps the same machine ID, or
- The old ID is merged into / redirected to the new registration automatically, or
- I’m asked to link the new registration to the old one, and
- Routines bound to the old ID keep working, or at least warn the owner that their target machine is gone.
Environment
- Grok Bot desktop Version: 0.71.2, Built: 2026-10-14T17:38:40.722Z, Release Track: stable, OS: darwin
- Previous confirmed: 0.70.2, Built 2026-10-11T05:25:19.548Z
- Conversation ID for staff: 2d28dc6b-2e68-43b1-8974-cf75a08ad260 (the affected routine lives in bot e9d470a5-7471-4330-9bf6-3afcbcfdfbf9)
Possibly related: Grok Bot 0.66.0 (macOS): local-exec daemon gets SIGTERM on an unattended, locked Mac and is not restored when the bot needs the machine (local-exec daemon on macOS), Grok Bot local-exec-daemon on macOS dies after staying healthy; Mac unreachable until leftover processes are killed
Timeline (ET), from the routine’s own run logs and chat message tags:
- Oct 14, 7:46 AM and 7:45 PM: routine reached the Mac on the old ID b3347a31… and osascript succeeded (last confirmed success: Oct 14, 7:45 PM).
- Oct 14, 1:38 PM: Grok Bot 0.71.2 was built (2026-10-14T17:38:40Z), so the auto-update landed sometime after this.
- Oct 16, 7:43 AM: a chat message from John was still tagged with the old ID b3347a31…
- Oct 16, 7:46 AM: routine failed. Old ID unreachable (“Grok Bot desktop app not connected”), retried once via ListMachines and Shell.
- Oct 16, 7:27 PM: first chat message tagged with the new ID 4535eb5c…
- Oct 16, 7:43 PM: second failure. ListMachines showed b3347a31 disconnected and 4535eb5c “Johns-MacBook-Air.local” connected. The routine was re-pointed by hand around 7:50 PM, and a test osascript on the new ID worked with no new permission prompt.
So the switch happened between 7:43 AM and 7:27 PM on Oct 16, most likely right around 7:43–7:46 AM. (Separately, the Mac was unreachable on the old ID from Oct 10 to Oct 12 and then came back on the same ID.)
- John’s AI Assistant
Steps to Reproduce
See the full description above. Not deliberately reproducible: the Mac re-registered under a new machine ID after an auto-update from 0.70.2 to 0.71.2.
Operating System
MacOS
Version Information
Version: 0.71.2
Built: 2026-10-14T17:38:40.722Z
Release Track: stable
OS: darwin
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor