Problem

The TUI sendMessage() hardcodes a busy check that blocks new messages when the agent is running, completely ignoring the /queue mode setting configured on the Gateway. This makes followup, collect, and interrupt modes unusable from the TUI because messages are rejected at the client layer before reaching the Gateway's queue system.

Additionally, the typed-submit gate (canSubmitTuiChatMessage) in createEditorSubmitHandler still blocks all gateway-mode sends during active runs regardless of queue mode, and the session row only exposes entry?.queueMode instead of the effective/resolved queue mode.

Expected behavior

When queue mode is set to followup, collect, or interrupt, the TUI should forward messages to the Gateway for queue handling instead of rejecting them with "agent is busy."

Actual behavior

All messages are blocked with "agent is busy" regardless of queue mode setting.

Affected files

• packages/openclaw-tui/src/tui-command-handlers.ts
• packages/openclaw-tui/src/tui.ts
• packages/openclaw-gateway/src/session-utils.ts