Skip to content

fix(chat): resume after server restart no longer reopens a closed chat#250

Merged
ericdallo merged 1 commit into
editor-code-assistant:masterfrom
rschmukler:rs/fix-chat-resume
Jun 11, 2026
Merged

fix(chat): resume after server restart no longer reopens a closed chat#250
ericdallo merged 1 commit into
editor-code-assistant:masterfrom
rschmukler:rs/fix-chat-resume

Conversation

@rschmukler

Copy link
Copy Markdown
Contributor

Resuming a previous session after a server restart reopened it as a "Closed session" buffer that rejected new prompts. eca-chat-exit' marks the most-recent chat buffer eca-chat--closed' on restart but leaves it in the session registry, so when the server replayed the chat via chat/open' -> chat/opened', the handler reused that stale closed buffer instead of creating a fresh one.

eca-chat-opened' now treats a registered buffer marked eca-chat--closed' as stale: it kills the leftover buffer and creates a fresh, writable one in its place. Adds regression tests covering the stale-closed and live-non-closed cases.

Resuming a previous session after a server restart reopened it as a
"*Closed session*" buffer that rejected new prompts. `eca-chat-exit'
marks the most-recent chat buffer `eca-chat--closed' on restart but
leaves it in the session registry, so when the server replayed the
chat via `chat/open' -> `chat/opened', the handler reused that stale
closed buffer instead of creating a fresh one.

`eca-chat-opened' now treats a registered buffer marked
`eca-chat--closed' as stale: it kills the leftover buffer and creates
a fresh, writable one in its place. Adds regression tests covering the
stale-closed and live-non-closed cases.
@rschmukler rschmukler force-pushed the rs/fix-chat-resume branch from 60accbc to 1c72f4b Compare June 11, 2026 15:40
@ericdallo ericdallo merged commit 12bcbda into editor-code-assistant:master Jun 11, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants