Detect session changes beyond counts in WebSocket stream
WebSocket streaming only emits a new session_update when the tuple of session id, status, and list lengths changes. If a discovery file is rewritten with new proposal/pattern/pain point content but the counts stay the same (a common update scenario), the signature stays unchanged and no update is broadcast, leaving connected clients with stale data despite new session snapshots. This undermines the new streaming feature’s goal of reflecting file changes in real time.
Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #15 (comment)
WebSocket streaming only emits a new
session_updatewhen the tuple of session id, status, and list lengths changes. If a discovery file is rewritten with new proposal/pattern/pain point content but the counts stay the same (a common update scenario), the signature stays unchanged and no update is broadcast, leaving connected clients with stale data despite new session snapshots. This undermines the new streaming feature’s goal of reflecting file changes in real time.Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #15 (comment)