Follow a conversation
A server-sent event stream (text/event-stream) of the conversation as it runs. It never reaches the computer: it shows what the conversation reports.
conversation: the conversation, at the start and on every change. transcript: native transcript lines as they are stored (session_id, file, offset, next_offset, size, data). delta: live updates the harness streams while the conversation is followed (seq, at, updates: ACP session updates, e.g. agent_message_chunk for reply text as it is written, tool_call, plan); conversations in an ACP app stream them, terminal sessions report their transcript per message.
From now by default; transcript_offset (with session_id) and after_seq start earlier. Each event’s id is the stream’s cursor: reconnect with Last-Event-ID (EventSource does) to resume. A stream ends periodically; reconnect to continue.
Request
- Base URL: https://api.shardflux.dev
- URL: https://api.shardflux.dev/v1/conversations/{id}/events
- Auth: HTTP bearer
Path parameters
Query parameters
Send stored transcript lines from this byte offset first.
Send live updates after this seq first (within the last few minutes).
Response
text/event-stream: conversation, transcript and delta events.
Changes
No recorded changes to this operation across all 1 revision of this API.