Skip to content

Isolate proactive messages by chat thread - #23

Merged
blackbartblues merged 1 commit into
mainfrom
agent/fix-chat-thread-isolation
Aug 1, 2026
Merged

Isolate proactive messages by chat thread#23
blackbartblues merged 1 commit into
mainfrom
agent/fix-chat-thread-isolation

Conversation

@blackbartblues

Copy link
Copy Markdown
Owner

What changed

  • binds proactive chat notifications to the thread that was active when they were created
  • keeps retry delivery bound to the original thread
  • preserves empty user-created conversations in the thread list
  • prevents live notifications for another thread from appearing in the open transcript
  • migrates legacy proactive messages to their original day thread

Root cause

Profile-wide chat_log rows were merged into whichever thread was currently active. In addition, a newly created empty thread was omitted from /api/chat/threads until its first Hermes message, so a refresh could select an older conversation again.

Impact

/new now remains a genuinely separate conversation after refresh, and old system alerts no longer reappear above every new user message.

Validation

  • backend: 375 passed
  • app: 218 passed
  • ESLint passed
  • TypeScript and Svelte checks passed
  • production app build passed

@blackbartblues
blackbartblues marked this pull request as ready for review August 1, 2026 11:06
@blackbartblues
blackbartblues merged commit 3f90cdb into main Aug 1, 2026
14 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.

1 participant