You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 86fcaed
Browse filesBrowse the repository at this point in the historyBrowse files
Preserve pending setup prompts and message action order
Keep pending model setup prompts and session recovery until dispatch or queue
insertion is accepted. Defer retries during another send, resolve readiness
and preset editing for the pending chat, and preserve new composer drafts.
Prevent retries from entering another selected chat's queue.
Preserve Detail, Copy, Speak order when actions are inserted or replaced,
without remounting unchanged controls. Add behavioral and browser regressions,
including preset-switch draft persistence, and update the WebUI contracts.
Validation: 84 focused tests passed; git diff --check passed.
Copy file name to clipboardExpand all lines: webui/AGENTS.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,7 @@
28
28
- Component HTML loaded by the shared loader may include `<title>`, module scripts, body content, and scoped styles; modal content uses the same loader path.
29
29
- Do not bypass WebSocket origin/auth/CSRF assumptions from frontend code.
30
30
-`index.js` rechecks the selected context after asynchronous snapshot hooks and message rendering; an older snapshot must not replace selection or sidebar state after a chat switch or creation.
31
+
-`index.js`'s `sendMessage` reports accepted dispatch or queue insertion with `true`; busy, rejected, or failed sends must not consume a setup-gate prompt. Release its send latch before resuming a deferred gate retry.
- Startup scripts in `index.html` must be local and non-parser-blocking: use ES modules, `defer`, or `async` for every script with `src`.
33
34
- Baseline main and login pages must load scripts, styles, fonts, and images from same-origin vendored or first-party assets so they remain usable without internet access.
Copy file name to clipboardExpand all lines: webui/components/chat/AGENTS.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@
12
12
-`navigation/` owns chat navigation state.
13
13
-`top-section/` owns chat header/top area.
14
14
-`model-gate-store.js` and `model-setup-gate.html` own the deferred in-thread model setup gate.
15
-
- Gate dispatch (`dispatchPendingIfConfigured`) must capture `pending`and raise its latch before any await, and re-verify pending identity after awaits; pending is never re-read from the store after an await point.
15
+
- Gate dispatch (`dispatchPendingIfConfigured`) captures `pending`before awaiting and uses that object for the payload; re-check its identity and the send latch after readiness resolves. Keep pending state and session recovery until the send is accepted. Busy sends defer retry until `sendMessage` settles; readiness and preset-editor reads use the pending chat's context. A retry for another context must never enter the selected chat's queue.
16
16
17
17
## Local Contracts
18
18
@@ -21,7 +21,7 @@
21
21
- Do not bypass CSRF or WebSocket state-sync expectations.
22
22
- The shared composer can be mounted on the Welcome screen with no selected chat; sending from that state must create and select a chat context before dispatch.
23
23
- Text-only and attachment sends must render the first user turn immediately with the request message ID so the backend log merges into the same row.
24
-
- Unsent composer text is kept as a separate browser-session draft for each selected chat and restored when switching contexts; a Welcome-screen prompt must follow the chat created for its first send.
24
+
- Unsent composer text is kept as a separate browser-session draft for each selected chat and restored when switching contexts; a Welcome-screen prompt must follow the chat created for its first send. Preset changes and setup-gate retries must preserve any new unsent composer draft.
25
25
- Composer text uses the main UI font by default; typing a triple-backtick fence and pressing Enter turns that line into a visual code block that serializes back to fenced Markdown, while pasted fenced Markdown stays plain text.
26
26
- The contenteditable composer sizes naturally between its CSS minimum and maximum heights; do not freeze measured scroll heights into pixels during mounting or editing.
27
27
- The backend rejects dispatches when no chat model is configured: a `user_message_ui` extension in `_model_config` flags the chat and `/message_async` returns a `model_not_configured` payload before logging or dispatching. The client opens the setup gate from that response and must not round-trip a per-send configuration pre-check.
Copy file name to clipboardExpand all lines: webui/components/messages/AGENTS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@
18
18
- Terminal output keeps text-size adjustment at 100% so mobile browsers do not inflate its wide, unwrapped content when streamed or expanded; preserve horizontal scrolling and normal browser zoom.
19
19
- Keep message action chrome out of text selection so copy/paste captures message content without button labels or icons.
20
20
- Reconcile standard action buttons in place during streamed updates so hover, focus, tooltips, and click feedback survive while handlers receive the latest message data; position buttons by index and never re-insert an already-mounted button, since re-inserting detaches and remounts it mid-stream. Preserve extension-owned buttons in the same action bar.
21
-
- Order standard message actions as Detail, Copy, then Speak; omit unavailable actions without changing the relative order of the remaining controls. Plugin-rendered message actions must follow the same order.
21
+
- Order standard message actions as Detail, Copy, then Speak; omit unavailable actions without changing the relative order of the remaining controls. Insert new or replaced actions before the next retained action or the stable extension anchor, never using a newly inserted action as that anchor. Plugin-rendered message actions must follow the same order.
22
22
- Collapsible action rows keep the hover-revealed `Show less` control laid out with reserved space on pointer devices; hover reveals it through opacity only so the row height never shifts, and its opacity fade matches the row fade so it never disappears ahead of sibling buttons.
23
23
- Keep collapsed process-step detail text out of the DOM; opening a step may materialize its current cached log data and collapsing it must discard that heavy detail again without removing extension action hooks.
24
24
- Preference-driven process detail modes must await the same materialization path as manual expansion and accept an explicit chat-history target for off-screen window staging. `STEP` opens only the current non-utility step at the live tail; historical windows must not invent a current step at their boundary.
0 commit comments