Member Junction
    Preparing search index...

    Client for the durable, resumable read of a conversation's agent-run progress (MJ #4222).

    The statusUpdates subscription is the only live path a conversation has and it has no replay: the server topic is an in-memory PubSub and the client subject is unbuffered. Anything published while the socket was half-open is gone, and the client cannot tell "nothing happened" from "I missed everything". This query is the durable counterpart — a client keeps the LatestSeq it has seen and re-reads from there after any interruption.

    Runs over plain HTTP, so it works while the WebSocket is still dead. That is the property the whole recovery path depends on.

    Index

    Constructors

    Methods

    • Read agent-run events for a conversation detail from a cursor forward.

      Parameters

      • conversationDetailID: string

        The message to tail.

      • sinceSeq: number = 0

        Highest Seq already seen; 0 or omitted reads from the start.

      Returns Promise<ConversationTailResult>

      Never throws — a transport failure comes back as Success: false with the caller's cursor preserved, because this IS the recovery path and throwing from it would break the reconciliation it exists to serve.