API Reference
Cinder.on
Subscribe to typed runtime events for scan, graph, resolve, dispatch, fallback, and speech activity.
Need the shortest path?
Use Quick Start when you want the smallest working route → scan → graph → run flow first.
Something feels off?
Inspect scan output, graph state, active route/context, and dispatch in a practical order.
Need the full surface?
Browse all runtime methods, hooks, extension points, and lifecycle APIs.
Use on() when you want structured runtime observability without patching internal code.
Example
ts
7 lines
Cinder.on('scan:end', (payload) => {
console.log(payload.durationMs, payload.mutationRescanCount);
});
Cinder.on('fallback:end', (payload) => {
console.log(payload.errorCode, payload.used, payload.latencyMs);
});Event names
scan:startscan:endgraph:updatedresolve:startresolve:enddispatch:startdispatch:endfallback:startfallback:endspeech:startspeech:endspeech:error
Why it is useful
Use runtime events for:
- debugging scan timing and mutation rescans
- tracing route/context updates
- monitoring fallback classification and usage
- observing speech lifecycle state
Safety note
Throwing event handlers are isolated so they do not crash runtime execution.
Related pages
Continue reading