Skip to content

Do not return a truncated provider transcript as a complete seed #541

Description

@dajiaohuang

The history seed reader stops after 20 pages but returns the events collected so far even when the last response still has a cursor. A long transcript can therefore be silently truncated and persisted/cached as if complete; reopening repeats the omission. The shared reader introduced in the open conversation-seed refactor retains the same 20-page cap and return behavior. When the cap is reached with a remaining cursor, surface an explicit incomplete/error state or continue safely rather than caching a partial seed as complete.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions