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
Opening a hosted team conversation can display its completed reply twice #1649
Opening a completed team conversation can display its final answer twice even though its transcript contains one assistant message. Reproduced during an ordinary invoice-tool workflow on 9a2c7cdd5: the checker ran the tool and reported once, but selecting its tab showed the same 536-character answer twice.
The two display inputs overlap: atomic AttachReplay returns the completed answer, while the hosted connection still offers the canonical turn through Follow. They have different channel identities, so channel-based checks do not recognize the replayed turn. A fix must preserve new replies (including identical text), in-flight observer output, and engine-restart ownership.
The original recording and single-message transcript are preserved. This is distinct from #1637, which concerns stream identifiers reused after an engine restart and a missing next reply. No fix or final verification is claimed yet.
Audited on current dev (39fdbea6f73c). #1632 (e7976208e3c8) landed the hosted replay ownership/coverage fix. Fresh transport checks passed for covered Follow versus a genuinely new turn, atomic observer replay, and old responses not replacing current ownership (1.024 seconds). Current display checks also passed: TestAReplayOntoADrawnConversationDrawsItOnce and TestASentenceTypedWhileTheRecordWasComingSurvivesTheReplay (part of a 0.061-second UI run). Closing as completed by #1632. This audit reran deterministic transport/display checks; it does not claim a new live-provider test.
Activity
Consolidate reviewed CodeAF fixes — batch 2 (#1632)
santoshkumarradha commentedon Oct 23, 2026
Audited on current
dev(39fdbea6f73c). #1632 (e7976208e3c8) landed the hosted replay ownership/coverage fix. Fresh transport checks passed for covered Follow versus a genuinely new turn, atomic observer replay, and old responses not replacing current ownership (1.024 seconds). Current display checks also passed:TestAReplayOntoADrawnConversationDrawsItOnceandTestASentenceTypedWhileTheRecordWasComingSurvivesTheReplay(part of a 0.061-second UI run). Closing as completed by #1632. This audit reran deterministic transport/display checks; it does not claim a new live-provider test.