-
-
Notifications
You must be signed in to change notification settings - Fork 79.1k
[Bug]: Feishu text commands (/stop, /new, /status) no longer bypass queue during active agent run (3.8 regression) #42803
Copy link
Copy link
Open
BingqingLyu/openclaw
#484Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingSomething isn't workingclawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.regressionBehavior that previously worked and now failsBehavior that previously worked and now fails
Metadata
Metadata
Assignees
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingSomething isn't workingclawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.regressionBehavior that previously worked and now failsBehavior that previously worked and now fails
Type
Fields
Give feedbackNo fields configured for issues without a type.
Bug type
Regression (worked before, now fails)
Summary
After upgrading to 2026.3.8, text commands (
/stop,/new,/status) on Feishu no longer execute immediately when an agent run is active. They are queued behind the current run and only execute after it completes. This worked correctly on 3.7 and earlier versions.Discord native commands are unaffected and still respond instantly.
Steps to reproduce
/stopor/statusor/newin the same Feishu DMExpected behavior
Per the docs ("Fast path: command-only messages from allowlisted senders are handled immediately (bypass queue + model)"), these command-only messages should bypass the queue and execute immediately, even during an active agent run.
Actual behavior
Commands are queued behind the active run.
/stopin particular becomes useless since you can't abort a long-running task until it finishes on its own.OpenClaw version
2026.3.8 (3caab92)
Operating system
macOS 26.3.1
Install method
npm global
Model
claude-opus-4.6
Provider / routing chain
N/A — not provider-related. Feishu websocket → OpenClaw gateway (local) → agent session. Bug is in command queue fast-path, not model routing.
Config file / key location
~/.openclaw/openclaw.json ; channels.feishu.connectionMode="websocket" ; messages.queue (default, no override)
Additional provider/model setup details
Not provider-related. This is a message queue / command fast-path issue.
Default model: claude-opus-4.6
Feishu channel: websocket mode, text commands only (no native command support)
Logs, screenshots, and evidence
Impact and severity
Affected: Feishu DM users on v2026.3.8
Severity: High (blocks workflow — cannot abort long-running agent tasks)
Frequency: 100% repro when agent run is active
Consequence: /stop, /new, /status commands are effectively unusable during active runs. Users must wait for full completion or switch to Discord to issue control commands.
Additional information
Last known good version: 2026.3.7
First known bad version: 2026.3.8 (upgraded 2026-03-09)
Temporary workaround: Use Discord native /stop command to abort active runs
Related: #12141 (similar symptom but reported as long-standing; this is a 3.8 regression)
Note: Feishu has no native command support, so all commands go through text parsing. The documented "Fast path" for command-only messages appears to no longer work on Feishu after 3.8.