Skip to content

[T1] Peek stream isolation #1362

Description

@dennisonbertram

[parent] #1339

Problem

Peek events indistinguishable from main/conversation stream events (model.go ~4496): dashboard peek can route foreign messages into transcript and freeze live rendering.

Outcome

Wrap peek messages in distinct msg type carrying channel identity; route only those to peek; always re-arm originating stream's poll.

Acceptance criteria

  • Peek active + live run → transcript keeps rendering; resumes after close.

Test-first plan

Peek-vs-live rendering regression test (expected red). HIGHEST priority.

Impact analysis

TUI-only.

Activity

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions