Chronos/DBWaitlist

Changelog / Chronos Gateway

Chronos Gateway 0.4.0

Engine 0.6.0; Runs are safe against lost answers and two decisions at once; Child runs

With Chronos DB 0.6.07 changesDownloads

  • Engine 0.6.0, which this release bundles: an agent held to a tenant is kept to its tenant's worlds and rows everywhere, every merge into main is logged with the rows it wrote in a hash-chained ledger (VERIFY LEDGER), and merges check the constraints they bring against rows the run never saw. Upgrading: the engine's first checkpoint or merge writes data format 8, which 0.5 can't open: back up the data folder before you upgrade.
  • Runs are safe against lost answers and two decisions at once. A run approved by the AI reviewer or through Chronos Cloud keeps its merge id, so it can be undone like one approved through the API. An approval always names the version it merges (the one the run was held at when the caller names none), never whatever the world holds by then. A run's status moves only from what it was read as: a person's approve, the reviewer, the cloud and the sweeper no longer overwrite one another (the second gets 409 run_changed). When a propose or approve times out, or the sweeper finds a run's world gone, the gateway asks the engine's history whether it merged and records it merged (reconciled: true) instead of expired; it checks live runs the same way when it starts.
  • Child runs. POST /v1/runs/:id/children delegates part of a run to a sub-agent: its own token, its world forked from the parent's, held to the parent's tenant and to no more than the parent may change. Its propose merges into the parent's world; the parent proposes once its children are done, and discarding it discards them. GET /v1/runs/:id lists children.
  • Effects delivered. With GATEWAY_EFFECTS (a receiver URL per channel) and GATEWAY_EFFECTS_SECRET, the gateway takes what merges queue in the engine's outbox (NOTIFY ON MERGE) and delivers each, signed, with its id as Idempotency-Key; retried with backoff, given up after GATEWAY_EFFECTS_MAX_ATTEMPTS (8). GET /v1/effects shows each one's status, attempts and receipt.
  • Evidence with a propose. POST /v1/runs/:id/propose takes evidence: [{kind, uri, sha256, note}], kept with the run (and attached to its world where the engine supports it). PATCH /v1/runs/:id/meta adds keys to a run's metadata.
  • Clients 0.3.0. Python: Run.undo(), Run.child(), Run.children(), Run.set_meta(), propose(evidence=), Gateway.effects(); adapters for CrewAI (crewai_tools), Pydantic AI (pydantic_ai_toolset, pydantic_ai_deps) and a LangGraph checkpointer (ChronosCheckpointSaver) that records each checkpoint on the run. TypeScript: run.undo(), run.child(), run.children(), gateway.effects(), propose({evidence}).
  • A merge the engine made is never recorded as rejected. A rejection or discard that finds the run's world already gone asks the engine's history first, and records the run merged when its merge landed (a rejection then gets 409 run_changed); an approval whose merge succeeded while a rejection or discard was recorded records it merged all the same (recorded_over in its outcome). Child runs count against GATEWAY_RUNS_PER_HOUR and are refused past it (429 too_many_runs) like any run. An effect whose channel has no receiver waits without using its delivery attempts. The reviewer's verdict no longer resets the version a part approval left. Python: the LangGraph checkpointer logs, and never raises, when the gateway can't be reached.
Chronos Gateway 0.4.0 · Chronos