#TUI /steer and queue UX
sand violet
This actually looks like how it works but I can see it’s confusing. You interrupted when you sent the queued msg, what happened after?
sand violet
Yeah I think this is basically intended but maybe not clear enough? You can change the mode to interrupt instead of queue too
stuck fern
The TUI's default busy_input_mode is queue, not interrupt — so typing while the agent is running appends to a queue rather than cancelling the turn. This is intentional: the TUI overrides the framework default (interrupt) to queue because an accidental interrupt while composing a follow-up loses work (ui-tui/src/app/useConfigSync.ts, TUI_BUSY_DEFAULT = 'queue').
To actually cancel a running turn, use Ctrl+C — that fires session.interrupt → agent.interrupt() directly (ui-tui/src/app/useInputHandlers.ts, ui-tui/src/app/turnController.ts).
/steer wouldn't have helped here. It injects text into the next tool result without interrupting the current turn (tui_gateway/server.py, session.steer handler) — it's for nudging a running agent mid-tool-loop, not for cancelling or re-routing a queued message.
If you want submitting a new message to cancel the in-flight turn instead of queuing, set:
display:
busy_input_mode: interrupt
daring raft
actaully i was trying to connect comet browser in hermes
