The Web chat receives a successful SSE done response for local commands such as /status, renders it, then immediately calls selectSession, which clears the transcript and reloads persisted messages. Local-command exchanges are not persisted, so the command and response disappear. Preserve the live transcript after a successful send while still refreshing session metadata.
Acceptance Criteria
Sending /status in the Web chat leaves both the user command and returned status visible; normal streamed replies remain visible; session catalogue metadata still refreshes; focused frontend tests and the repository quality gate pass.
Imported from beads archie-core-1786637490593-31-bcb624f5 · GitHub #52 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08
The Web chat receives a successful SSE done response for local commands such as /status, renders it, then immediately calls selectSession, which clears the transcript and reloads persisted messages. Local-command exchanges are not persisted, so the command and response disappear. Preserve the live transcript after a successful send while still refreshing session metadata.
### Acceptance Criteria
Sending /status in the Web chat leaves both the user command and returned status visible; normal streamed replies remain visible; session catalogue metadata still refreshes; focused frontend tests and the repository quality gate pass.
---
_Imported from beads `archie-core-1786637490593-31-bcb624f5` · GitHub #52 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam
added the mediumbug labels 2026-10-27 13:36:48 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The Web chat receives a successful SSE done response for local commands such as /status, renders it, then immediately calls selectSession, which clears the transcript and reloads persisted messages. Local-command exchanges are not persisted, so the command and response disappear. Preserve the live transcript after a successful send while still refreshing session metadata.
Acceptance Criteria
Sending /status in the Web chat leaves both the user command and returned status visible; normal streamed replies remain visible; session catalogue metadata still refreshes; focused frontend tests and the repository quality gate pass.
Imported from beads
archie-core-1786637490593-31-bcb624f5· GitHub #52 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08