Context runtime
The interaction layer for AI workflows.
Events owns the durable conversation and execution trail. UI components render that surface, while the package keeps context state, model reactions, domain actions, and replay out of the registry.
/events
Events surface
schema
event_contexts
The aggregate root for a durable AI interaction, addressed by id or key.
event_items
Stored user and assistant items that make up the turn history.
event_executions
Reaction runs attached to a context, including status and runtime metadata.
event_steps
Execution-level steps for reasoning, action calls, and observable progress.
actions
createContext
Builds a registered context with narrative, skills, actions, model, and reactor.
defineAction
Declares typed domain actions that a context reaction can call.
createAiSdkReactor
Adapts AI SDK model action-call output into canonical event items and parts.
runContextReactionDirect
Executes a context reaction without registry-specific UI glue.
EventContextPanel
Interactive panel for rendering an event context timeline and appending input through the canonical events React API.
From simple to complex
The same idea, three depths.
in one sentence
A durable memory for AI conversations.
Everything the agent saw, said, and did — saved as data you can read back anytime.
how it works
Append a message, the agent reacts, every step lands as a record.
You open a context for a conversation and append items to it. The agent reacts with the model and your domain actions, and each piece of its work — text, reasoning, action calls — is persisted as it happens. UI reads that same record reactively, so what you render is always what actually occurred.
under the hood
Contexts, items, executions, steps, and parts on a typed schema.
event_contexts is the aggregate root; event_items hold the turn history while event_executions and event_steps track each reaction run, and event_parts are the canonical replay surface. Actions like createContext, defineAction, and createAiSdkReactor wire models and typed domain actions into that durable trail.
Route contract
Landing, UI, and library are separate surfaces.
Runtime shape
Package behavior. Registry presentation.
Events is the first published UI surface because product apps already need to render live context state, prompt input, history, and execution progress.
package
@ekairos/events@beta
aggregate
event_contexts
durable
event_parts
ui
26 component listed