/stop

Immediately stop the Bee that is currently processing in this chat and cancel any messages that are queued but not yet processed. The command is session-scoped — it only affects the chat you send it in.

Syntax

/stop     # Stop the running Bee and cancel pending messages in this session

/stop takes no arguments.

Responses

The reply you receive depends on what was actually running when you sent the command:

How It Works

When you send /stop:

1. Bee cancellation — If a Bee execution is in progress, its Go context is cancelled. Cancellation propagates immediately through the entire execution pipeline; the Bee stops at the next context-aware checkpoint without waiting to finish the current turn.
2. Pending message cleanup — Any messages in received status (queued but not yet picked up by the Bee) are marked failed. This prevents the Bee from automatically resuming on those messages once the stop clears.

/stop does not clear conversation context, stop Worker executions, or cancel scheduled tasks. For those, use /clear.

When to Use /stop

• Interrupt a long-running response. The Bee is taking too long or went off track — send /stop to cut it short immediately.
• Cancel a queued message. You sent a message and changed your mind before the Bee processed it — /stop removes it from the queue.
• Recover from a stuck Bee. If the Bee appears frozen and not responding, /stop forces the execution to terminate.
• Stop before a /clear. When you want a clean slate: /stop first to drain in-flight work, then /clear to wipe context.

Notes

• Idempotent — calling /stop when nothing is running is safe; you receive Nothing to stop in this session and no state changes.
• Session-scoped — only the chat you send /stop in is affected; other sessions continue uninterrupted.
• Message records are preserved — stopped messages are marked failed in the database, not deleted.
• No confirmation required — unlike /clear with running tasks, /stop executes immediately without a second prompt.