Grok Bot: a scoped "stop" to one bot cascaded into a stop-all across every teammate bot

Support Bug Reports
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Severity: critical. On 10/29/2026 at 2:07 PM ET, I told one of my Grok Bot agents to “stop”, meaning only that bot’s own current task. The bot ran a stop-all instead, which cancelled the in-flight turns and subagents of all 10 of my other teammate bots. Scheduled routines were not affected.

Steps to Reproduce

See description above.

Expected Behavior

Expected: a stop request stops only that bot’s own work. Stopping every peer bot should need an explicit instruction (“stop everyone”) or a confirmation first.

Operating System

MacOS

Version Information

Grok Bot desktop app, macOS

Additional Information

Workaround: I added a memory rule to that bot. I also sent this through in-app feedback.

Ref: KAN-180

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

4

Proposed expected behavior: a “stop” command should only pause the bot’s current action in flight. If other routines within the bot are firing at the same time, the bot should ask the user a decision question on a card. If multiple routines are firing at once, the bot should pause based on the user request that was being worked on, then ask questions from there. Ref: KAN-180