On this page
Conversation composer and delivery indicators
This reference covers the ordinary Chat message box, not provider setup, voice input or answer fields in decision cards. It describes source behaviour; it is not a keyboard/accessibility certification.
Before sending: a model request can send composed context to the configured endpoint and incur charges. See preparation and the conversation explanation.
Message controls
| Control or state | Source-defined behaviour | Important boundary |
|---|---|---|
| Enter in the ordinary message box | Attempts to send non-blank text, unless the input-method composition guard applies | Do not press Enter merely to prepare a screenshot. The keyboard handler does not use the button's busy-state cancellation branch. |
| Shift+Enter in that box | Does not take the Enter-to-send branch; the textarea's ordinary newline behaviour is left in place | Actual keyboard, input-method and accessibility behaviour still needs observation. |
| Send button when not thinking | Attempts to send non-blank text | A displayed pending card is not a saved-message receipt. |
| Same button while thinking | Sends a cancellation request instead of sending the typed text | A request to cancel is not confirmation of cancellation, erasure, cost reversal or undo of completed effects. This is not a tested cancellation procedure. |
| Disconnected before sending | Shows “not connected — reconnecting” and declines the send attempt | Other requests already in flight can still have uncertain outcomes. |
| Twenty unresolved pending cards | Declines another send and asks for resolution or dismissal | Do not dismiss cards solely to bypass the limit before preserving and reconciling their information. |
| Dismiss on a pending card | Removes that card and its local pending entry | Does not send a cancel request or delete recorded history. It removes a useful place to inspect the pending text. |
On a successful UI submission attempt, the composer clears its text and displays a pending card. A cleared box is not evidence of successful recording. Whitespace-only input is not sent; submitted text is trimmed.
Read delivery indicators narrowly
| Indicator | What it establishes — and does not |
|---|---|
| Sending — awaiting confirmation | The dashboard made a send attempt; host acceptance and saving are not established. |
| Accepted — waiting to be recorded | Host admission was reported, not durable recording or a model answer. |
| Not accepted — your text is kept here | Admission was refused; preserve the text and error before deciding what to do next. |
| Connection lost — delivery unconfirmed | The UI cannot establish the outcome; this is not proof that nothing happened. |
| Not recorded / Recording unconfirmed | A recording error was reported. Read the exact error; a transient copy, if offered, is not saved history. |
| Conflicting recording confirmations | The dashboard cannot reconcile the confirmations. Do not choose whichever is most convenient or resend automatically. |
| Not saved — your words are in this session's transient view | Session visibility is not durable storage. Do not rely on survival across restart. |
An error-free recording receipt removes the pending card; it can refer to recorded or transient content. Card disappearance alone is not a durable-recording guarantee. A generated reply can also be visible when its own recording fails.
For conservative next steps, see setup and delivery problems. Exact history-navigation, cancellation outcomes and recovery execution still need live replay.