Transactional reducers
Rust WASM and TypeScript modules mutate data beside storage. Rust WASM reducers validate changes before commit. TypeScript reducers currently require memory mode.
Developer preview
Cosmictron is being built around products where agents, customers, and operators carry work forward together. The goal is shared application state that connects progress, decisions, and ownership of the next step.
Developer preview. The integrated agent experience is a development objective. Memory integration, coordination, and autonomous restart recovery still need release verification.
What you can build on
A module owns its tables, reducers, and read procedures. Clients connect through WebSocket, PgWire, or HTTP. Supported live SQL results travel back over the authenticated WebSocket session. These capabilities are foundations for evaluation, not proof of a complete collaborative agent product.
Rust WASM and TypeScript modules mutate data beside storage. Rust WASM reducers validate changes before commit. TypeScript reducers currently require memory mode.
Supported SQL subscriptions follow committed changes. DBSP join and aggregate foundations are implemented, but their WebSocket delivery is not yet available.
An authenticated WebSocket session registers the SQL subscription and receives its incremental deltas.
SQL query interfaces complement the WebSocket gateway. Live SQL subscriptions use WebSocket.
Email and password, passkeys, and magic links establish a session identity that row-level policies can reference.
Modules define tables, reducers, and read procedures beside the storage engine.
Access stays with the table
#[table(name = "documents", public)]
#[rls(read = "owner_id = ctx.sender OR ctx.sender IN (...)")]
#[rls(write = "owner_id = ctx.sender")]
pub struct Document {
#[primary_key] pub id: u64,
pub owner_id: Identity,
pub title: String,
} Supported subscription snapshots and deltas are filtered using the caller's identity. Rust WASM reducers check write policy before commit. TypeScript reducers do not yet enforce these write-policy checks. The same identity follows the caller from the authenticated session.
When a durable write succeeds but later finalization fails, the server reports an uncertain commit outcome. Applications must reconcile that outcome before retrying a mutation.
In development
Memory helps an agent remember. The intended product also connects who owns the next step, what is approved, what changed, and what customers and operators see. Session, tool-authorization, and live-update foundations are in the server. Integrated coordination, durable autonomous agents, and their memory layer remain in development.