Expand description
Durable runtime history in the application’s existing SQLite database.
Every handle is bound to one workspace. State changes and their events commit together. Event sequences are allocated by a write statement, avoiding a read/modify/write race between concurrent writers. Timestamps are Unix ms.
Structs§
- Accounting
Overflow - Agent
Checkpoint - Versioned execution snapshot. Runtime code owns the state schema; it must include resolved resource/model, conversation, workspace and policy context.
- Agent
Event - One immutable event; sequence numbers are local to a run and start at one.
- Agent
Run - Materialized state of an execution. Inputs and outputs are plain text.
- Agent
RunStore - Workspace-scoped persistence facade, sharing the application connection pool.
- Artifact
Metadata - Metadata for an immutable file stored beneath a run’s artifact directory.
- Budget
Row 🔒 - Continuation
RunRow 🔒 - RunBudgets
- RunLineage
- Immutable ancestry of a run. Legacy runs without a row are treated as roots.
- RunSuspension
- RunUsage
- Stopped
Run 🔒 - Tool
Invocation - Working
State Artifacts - Working
State Event Reference - Working
State Inspection - Working
State Objective - Working
State 🔒Row - Working
State Run - Working
State Snapshot
Enums§
- Blocked
Reason - Budget
Decision - Failure
Reason - Limit
Reason - Needs
User Input Reason - Recovery
Disposition - A read-only classification of the durable state available for recovery.
- RunLifecycle
- RunOutcome
- A stopped transition; callers cannot create arbitrary lifecycle strings.
- RunOutcome
Kind - Token
Accounting - Tool
Outcome - Working
State Status