Skip to main content

Module events

Module events 

Source
Expand description

Event types for omne pipe execution.

Seven v1 event types per the v2 design doc. Serialized as JSON Lines to per-run .omne/var/runs/<run_id>/events.jsonl. Each event is discriminated by a top-level type tag.

Call sites land in later units (event_log, executor); the module carries #[allow(dead_code)] until then.

Structs§

GatePassed
Input
One --input key=value pair carried on pipe.started.
IterationStarted
Marks the start of one iteration inside a loop node. Emitted once per iteration from the executor. The byte_offset is the zero-based byte position in the node’s capture file (nodes/<id>.out) at which this iteration’s assistant output begins — immediately after the executor’s iteration marker line. Agents reconstruct per-iteration text by slicing [byte_offset_N .. byte_offset_{N+1}) (or to EOF for the final iteration) without having to parse the marker format.
NodeCompleted
NodeError
Structured error payload nested under NodeFailed.error.
NodeFailed
NodeStarted
PipeAborted
PipeCompleted
PipeStarted
Field conventions shared by every event type:

Enums§

ErrorKind
Reason a node failed. Serializes as snake_case under error.kind.
Event
All v1 event types.
GateMethod
Gate-pass method. In v1 only Hook is emitted; HumanCli and McpTool are reserved for post-v1 and included now to avoid a schema break.
NodeKind
Node execution kind, carried on node.started.