The short answer

Agent Room LiveView combines Room and operational projections behind a Room-scoped interface. Clients resume with composite durable cursors because the contributing sources do not necessarily share one sequence. SSE delivers changes; retained state determines their meaning.

One interface can include several operational sources

A Room screen may need the aggregate, current execution sessions, Handoffs, contributions, plans and external delivery status. Fetching only the message history leaves much of the work invisible.

The LiveView reference describes server-side discovery of these Room-scoped projections. Optional client-supplied identifiers narrow the view; the client does not need to enumerate every identifier to discover relevant operational state.

A composite cursor is not one global event number

Different projections may advance on separate sequences. LiveView therefore uses a composite multi-source cursor for bounded pages and its versioned stream. Treat that cursor as the service's continuation token rather than manufacturing a single counter from arrival order.

In an illustrative dashboard, a contribution update can arrive near an execution-session change without implying that they share one physical ordering. Display their recorded relationships and timestamps where useful, but avoid inventing causal dependencies from which network frame arrived first.

Reconnect from persisted progress

The API contract documents bounded event reads, optional SSE endpoints and request cancellation. A reconnecting client should use its durable cursor and handle the returned versioned envelope.

A practical client design persists the last successfully applied continuation position, resumes from it and makes repeated application harmless. Do not mark a task complete when the connection closes. A disconnect can mean a lost network path while the work continues normally.

Understand the database side of the stream

The operational migration chain includes Room-scoped transitions recorded in the same transaction as source state, followed by durable projector high-water checkpoints. This matters because a projector can stop after applying an effect but before saving local progress.

The migration reference identifies the operational stream and projection-checkpoint capabilities. Verify that the deployed schema includes the capabilities your interface depends on. Adding an SSE connection cannot compensate for a missing persisted projection.

Test the view through disconnection and replay

  • Open a Room with work in more than one projection.
  • Disconnect the client while the work changes.
  • Resume from the retained cursor and inspect all discovered sources.
  • Reapply an already-seen update and check the view for duplication.
  • Compare displayed terminal status with persisted domain state.

These recommended checks target interface correctness, not delivery guarantees for every network. Keep the versioned envelope and cursor contract visible in client tests so future changes cannot silently replace durable resumption with a best-effort live feed.

Sources and further reading

Documentation reviewed . Consult the linked documentation for current implementation details.