When the user has typed something into the composer and hits Enter, the
message goes to one of four fates depending on engine state:
- Immediate (idle + online) — most common, sends right away
- Steer (busy + tool execution) — forwards mid-turn
- QueueFollowUp (busy + streaming text) — parks for after TurnComplete
- Queue (offline) — parks on offline queue
Previously the user had no way to tell which would fire BEFORE pressing
Enter. The disposition flips with fast-changing internal state (whether
the model is currently streaming text vs. running a tool, whether
network connectivity has just dropped) and only the post-submit status
toast hinted at the result — which is too late if you wanted a different
behaviour.
Fix: extend the composer's bottom hint line so when the composer has
non-empty content, it shows what Enter will do RIGHT NOW. The hint flips
live with engine state, so the user sees the real behaviour before
pressing Enter:
↵ steer into current turn (sky blue, busy + tool execution)
↵ queue for next turn (muted, busy + streaming)
↵ offline queue (no engine) (warning yellow, offline)
The Immediate case stays unhinted — that's the default and surfacing it
would be noise.
Closes#345.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Hunter Bown
bc13dbfee7