Skip to content

Opening a hosted team conversation can display its completed reply twice #1649

Closed

Description

@santoshkumarradha

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.

Activity

  1. added
    area:chatThe v3 surface a person sits in front of (internal/tui3)
    sev:papercutA wording, a hint, a small wrongness that costs a moment
    on Sep 28, 2026
  2. santoshkumarradha commented on Oct 23, 2026

    @santoshkumarradha
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:chatThe v3 surface a person sits in front of (internal/tui3)bugSomething the code does that it should notsev:papercutA wording, a hint, a small wrongness that costs a moment

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions