cef-cubby-state

Persist per-entity state for CEF agents by configuring a cubby alias in cef.config.yaml, then utilizing ctx.cubbies and the Cubby API to execute SQLite queries, run migrations, and maintain isolated durable state.

Manage cross-agent state sharing safely by using per-entity cubby instances with explicit instanceId usage, which enforces per-entity isolation and prevents data conflicts across concurrent agent workloads.

SQLite supports vector storage for agent state management through the sqlite-vec extension, enabling you to store and manage vector data within the persistent cubby state layer alongside traditional relational data.

Run database migrations to define schemas for agent state by using the migrations-defined schemas approach within the Cubby API, which requires inline handler code and explicit instanceId usage to ensure production reliability.

You can implement state machine patterns, deduplication, and buffered flush within SQLite using the Cubby API, which provides a centralized, persistent storage layer designed for safe cross-agent sharing and per-entity isolation.

Explicit instanceId usage is required when querying persistent cubby state to guarantee per-entity isolation and safe reads, preventing data leakage across concurrent CEF agent workloads in production deployments.