Status

What works, and what isn't ready.

Developer preview · Updated 8 October 2026

This page exists so every claim elsewhere on the site has a place to be checked. The homepage keeps "asks first" and "receipts" as features, not as the headline, until an independent re-probe of the 2026-10-02 audit batch and its follow-ups (v0.6.28–v0.6.37) is run. A review on 8 October re-checked 63 focused tests — output guards, governance, approvals, the execution kernel and the synthetic reference — and they pass. That is not a full-suite, live-provider or hostile-tenant sign-off.

Ready now

  • Local single-user mode — runs on the OS account you already have; the localhost API is unauthenticated by design.
  • Shared deployment key for trusted access, plus opt-in per-user keys (PER_USER_AUTH=true) and browser OIDC integration — deployment teams configure and test them.
  • Permission policy — every tool call resolves to allow, ask, or deny, and gated actions keep a durable proposal.
  • Explicit outcomes — receipts record succeeded, failed, refused, timed out, cancelled, or uncertain instead of inferring success from response text.
  • Local storage and memory — HybridDB and CoreMem run in-process; no hosted service required.
  • Bring your own provider — local (Ollama) or cloud (OpenAI, Anthropic, Gemini); ModelPanel keeps keys on your machine.
  • MIT license — every layer of the stack.

Not ready yet

  • Individual accounts are not the default — the shared API_KEY is trusted-deployment access, not per-user identity. Per-user keys and OIDC exist as opt-in and must be configured and tested; a client-supplied user_id is not authority.
  • Hostile-tenant isolation in one shared server — mode 3a runs on a shared uid. Dedicated containers (3b) exist, but startup and isolation must be validated in the chosen environment.
  • Finished native SSO, organisation-wide sharing or roles, and verified multi-instance login.
  • A finished native macOS product — the client is an experiment, and product work is parked.
  • Security certification — no SOC 2, ISO 27001, or HIPAA/BAA support. Do not put regulated data in it yet.
  • Paid or independent adoption — no customers and no paid pilots yet; the synthetic reference is not customer proof.

How to verify