-
-
Notifications
You must be signed in to change notification settings - Fork 79.1k
OpenClaw TUI busy input lock prevents queueing prompts, unlike Telegram #86673
Copy link
Copy link
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape 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:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.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.
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape 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:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.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.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Area
OpenClaw TUI
Problem
When an agent is running in the OpenClaw TUI, the input area shows:
agent is busy — press Esc to abort before sending a new messageAt this point, the user cannot submit another prompt. This means the prompt cannot enter OpenClaw's queue system at all.
Expected behavior
While an agent is busy, the TUI should allow the user to submit a new prompt and let OpenClaw handle it according to queue behavior, for example:
Actual behavior
The TUI blocks submission before the message enters OpenClaw. The user has to type a follow-up prompt and wait with it sitting in the input box until the current run finishes.
Difference from Telegram
In Telegram, I can continue typing and sending messages while the agent is busy. Those messages can still enter OpenClaw and be handled asynchronously.
In the OpenClaw TUI, however, submission is blocked by the busy input lock before the message enters OpenClaw. This makes the TUI behavior different from Telegram and prevents the queue mechanism from being useful there.
Why this matters
For long-running tasks, this prevents async workflow. The user cannot leave follow-up instructions in advance and step away.
What I tried
messages.queue.mode=steermessages.queue.mode=interruptmessages.queueto default / removed custom queue settingsCurrent understanding
steer,interrupt, andcollectappear to apply only after a message enters OpenClaw. The TUI busy lock prevents the message from entering the queue in the first place.Request
Please clarify whether the TUI busy input lock is intentional. If queueing prompts during a running agent is intended to be supported, the TUI should allow prompt submission while busy, or provide a setting to enable it.