Skip to content

v1.9.0-ce — The Autonomous Database (CREATE AGENT)

Released: 2026-07-13 · Tag: v1.9.0-ce · Docker: synapcores/community:v1.9.0-ce

The flagship of v1.9 is CREATE AGENT: durable, governed AI agents that live inside the database as first-class schema objects. An agent is a persona bound to a task, one or more activations (a schedule and/or DML events), a governance envelope, and persistent memory. You INSERT a row; the agent wakes up and acts — no external cron box, worker fleet, or queue to operate.

CREATE AGENT — durable agents

CREATE AGENT incident_triage
  PERSONA 'aidb-assistant'
  TASK 'Triage the incident in the activation row: classify it, name the likely
        attack pattern, and recommend an escalation tier.'
  ON INSERT INTO incidents WHERE severity = 'critical'
  WITH (max_iterations = 3, allow_writes = FALSE,
        timeout_seconds = 90, budget_tokens_per_day = 200000,
        on_budget_exhausted = 'pause');
  • Full DDL family: CREATE / ALTER / DROP / SHOW / DESCRIBE / EXECUTE AGENT.
  • Activations: ON SCHEDULE '<cron>' (5- or 6-field) and/or ON INSERT/UPDATE/DELETE INTO <table> [WHERE …]. Event bindings are internal after-triggers — a non-matching write pays sub-millisecond overhead and never runs inference on the write path.
  • Restart-durable: definitions reload, cron schedules re-arm (process-global scheduler), queued invocations drain.
  • Governance: per-agent iteration cap, allow_writes, timeout, and a daily token budget enforced at dispatch. Budget exhaustion auto-pauses the agent (visible in SHOW AGENTS). Agent-initiated writes never re-trigger event bindings (cascade suppression).
  • Auditable: every run lands in the read-only _system_agent_runs table — activation, status, tokens (with a tokens_estimated honesty flag), duration, output. Run history retained 30 days.
  • CE limit: 10 active agents per instance.
SHOW AGENTS;                     -- name, persona, bindings, state, tokens today
DESCRIBE AGENT incident_triage;  -- full definition + governance
EXECUTE AGENT incident_triage;   -- run once, synchronously
SELECT * FROM _system_agent_runs WHERE agent_name = 'incident_triage' ORDER BY started_at DESC;

Also in v1.9.0

  • Native cross-encoder reranker: MEMORY_RECALL supports two-stage rerank via a native GGUF cross-encoder (bge-reranker) — retrieve wide by vector similarity, re-score the top-K with a cross-encoder. Rides the in-process model registry; no extra service, no ONNX, no GPU.
  • synapcores import <gguf>: install a local GGUF file as a registry model (offline/air-gapped provisioning).
  • Reliability: model-resolution honors per-call/per-agent overrides and fails loudly on unknown model names (R1c); a CREATE TABLE → INSERT schema-visibility race on the hot path is closed (R1e); SQL correctness batch (GROUP BY + ORDER BY resolution, comment-aware recipe splitter, aggregate NULL column-length).

Validation

  • State-asserting validator: 88/88, 0 failed.
  • Recipe certification: 158/159 (the lone failure predates this release — fails identically on v1.8.9-ce).
  • Non-AVX-512 canary (i5-10400F): config-pure boot, native EMBED + GENERATE, and CREATE AGENT + EXECUTE AGENT all working out-of-the-box, zero illegal-instruction.

Install

docker pull synapcores/community:v1.9.0-ce
# or pin the installer:
curl -fsSL https://get.synapcores.com | SYNAPCORES_VERSION=v1.9.0-ce sh

Upgrading from v1.8.x is drop-in — no schema migration; durable agents are opt-in.