Events and Journal

Event translation

The mapper (mapFlueToEve()) converts Flue runtime events to Eve events line-by-line:

Flue event	Eve event
`agent.start`	`agent.start`
`agent.message`	`agent.content.delta` → `message.appended`
`agent.tool_call`	`agent.tool_call`
`agent.tool_result`	`agent.tool_result`
`agent.complete`	`agent.complete`
`result.completed`	`result.completed`

MCP tools from Flue connections are renamed to use the connection__ prefix:

Flue tool: mcp__linear_search_issues
Eve event: tool_call { name: "connection__linear_search" }

This mapping is handled by @flue-eve/connections and the mapper automatically.

The mapper handles park/resume cycles:

Scenario	Events
Human-in-the-loop	`input.requested` → (client sends `inputResponses`) → resume
OAuth authorization	`authorization.required` → (callback completes) → `authorization.granted` → resume

The event journal is the sole owner of streamIndex. Every translated event is appended with an incrementing index. This enables:

Client reconnects with ?startIndex=N
Compat-server reads journal entries from index N onward
If tail mode (no startIndex or beyond current journal), server waits for new events
Events are streamed via NDJSON, one per line

Configure journal persistence per deployment.

Event	When emitted
`session.started`	New session created
`agent.start`	Agent turn begins
`agent.content.delta`	Streaming text fragment
`message.appended`	Complete message state update
`agent.tool_call`	Tool invocation started
`agent.tool_result`	Tool result returned
`agent.complete`	Agent turn finished
`result.completed`	Structured result (when `outputSchema` used)
`session.waiting`	Session ready for next turn (unlocks composer)
`session.failed`	Terminal error
`input.requested`	HITL — waiting for user input
`authorization.required`	OAuth — waiting for connection auth

For the authoritative Flue → Eve event mapping, see eve-to-flue mapping.