Skip to content
CCinder
Cinder.on

API Reference

Cinder.on

Subscribe to typed runtime events for scan, graph, resolve, dispatch, fallback, and speech activity.

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:start
  • scan:end
  • graph:updated
  • resolve:start
  • resolve:end
  • dispatch:start
  • dispatch:end
  • fallback:start
  • fallback:end
  • speech:start
  • speech:end
  • speech: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.

Continue reading