Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
The same Grok Bot appears to have been running as two separate backend/runtime instances on macOS and Android at the same time.
At approximately September 7, 2026, 18:00 UTC (September 8, 2026, around 02:00 Beijing Time / UTC+8), I noticed that scheduled tasks from the same bots were sending me different results on macOS and Android.
I have two affected bots:
54446ec9----********145a
c08f17c5----********c13a
I can provide the complete IDs privately if needed.
After interacting with the same bot from both platforms, I found that the conversations were no longer synchronized. Messages sent to the bot on macOS were not reflected in the Android instance, and vice versa.
The Android instance also appeared to have been recreated or restored from a separate environment:
Its computer screen had been cleared and showed only an empty desktop.
A scheduled task reported that its Python virtual environment had disappeared/been cleared, so it automatically recreated it.
Despite this, both the macOS and Android instances reported almost identical system information, including the same hostname, kernel, machine-id, LAN configuration, and bot/agent ID.
Their public/outbound IP addresses were different.
For example, the Android instance of:
c08f17c5---****-********c13a
reported approximately:
hostname: cursor
kernel: Linux 6.12.94+ x86_64
machine-id: 901a41e8************04d1
LAN IP: 172.30.0.x/24
interface: enp0s3
Docker bridge: 172.17.0.x
MAC: 82:2b:38:xx:xx:d0
Bot/Agent ID: c08f17c5----********c13a
Public IP: 104.30.xxx.xxx in most checks, while one route returned 95.135.xxx.xxx
The macOS-side instance reported essentially the same internal system information and the same agent ID, but a different outbound/public IP.
I also created a new Grok Bot on Android as a synchronization test. The newly created bot did not appear on macOS.
After restarting the Grok Bot app on macOS, the macOS state suddenly synchronized with Android. The previous macOS-side instance disappeared, and the bot state became consistent with the Android version.
This suggests that macOS may have remained connected to a stale or duplicated backend instance while Android was connected to another instance of the same bot.
My main concern is that scheduled tasks may have been running independently on both instances, resulting in duplicate execution and potentially double usage/credit consumption.
Steps to Reproduce
This issue was not intentionally triggered, so I do not currently have a deterministic reproduction method.
The sequence I observed was:
Have the same Grok Bot account active on both macOS and Android.
Have existing Grok Bots with scheduled tasks enabled.
At approximately September 7, 2026, 18:00 UTC, observe scheduled-task notifications on both platforms.
Notice that the same bot sends different scheduled-task results on macOS and Android.
Start conversations with the same bot independently from both platforms.
Observe that the conversations no longer synchronize between macOS and Android.
Ask each instance to report runtime/system information.
Observe that they report nearly identical internal identity information, including the same machine-id and bot/agent ID, despite having different runtime/conversation state.
Create a new Grok Bot on Android.
Observe that the newly created bot does not appear on macOS.
Restart the Grok Bot app on macOS.
Observe that macOS then synchronizes with the Android state and the previously active macOS-side instance disappears.
Expected Behavior
The same Grok Bot should have a single consistent state across all supported clients.
Specifically:
macOS and Android should access the same bot/conversation state.
Messages sent from one platform should be visible from the other platform.
Creating a new bot on one platform should make it appear on the other platform after synchronization.
A bot should not have multiple independently active runtime instances executing the same scheduled tasks unless this is explicitly intended.
Scheduled tasks should execute only once per scheduled run.
A stale client or stale backend session should not continue consuming usage independently after the bot has migrated or been recreated elsewhere.
Restarting a client should not be required to resolve a backend-state split.
Operating System
MacOS
Version Information
MacOS
Version：0.44.0
Channel：stable
OS：darwin
Android:
Grok Bot 1.8.0 (177) · runtime 97555d673679899f2c5eb35cf380c1c61574cfd6 · embedded bundle · channel production
Does this stop you from using Cursor
No - Cursor works, but with this issue