This article is retained from the existing framework docs. Self-hosting commands and server-admin access differ from the managed CLI workflow. Start with Get started for the installed product.
Events API
Read stored traversal events or follow progress through an event stream.
Live node-log SSE for one root (root_id) or one step (traverser_id). id is the log sequence cursor; send Last-Event-ID to resume after the last consumed line. Each log event carries one LogRecord; levels, stream, contains, since and until filter exactly as GET /api/v2/logs. Comments are keep-alives. The stream ends with an end event once the subject is terminal and no further lines arrived during a short grace window; an error event reports a refused query. Requires node log ingestion to be enabled for the namespace, otherwise the log table is simply empty.
Durable ordered execution SSE. id is a monotonically increasing sequence cursor. Send Last-Event-ID to resume after the last consumed event. Comments are keep-alives. Clients must deduplicate on reconnect and stop after the subject's terminal event; child terminal events do not terminate the root stream. Buffers must be bounded. This is not an LLM token stream.
Python SDK: Client.events(traverser_id) is the maintained async SSE iterator with cursor reconnection, separate from generated JSON request/response routes.
Parameters
Parameter
In
Required
Type
id
path
yes
string
Last-Event-ID
header
no
string
Responses
Status
Body
Meaning
200
string
Execution events; each data field is an ExecutionEvent JSON object