What ships today.

Operable today through the documented install path — the shell installer or the web app.

• CLI run --now / --share / --prlive

  Run one task locally, get a scored receipt, optionally publish a public paste or open a PR with the receipt as the body. No account needed for local runs.

• Per-CLI config generationlive

  init detects your stack and writes CLAUDE.md, AGENTS.md, and .cursor rules from one ai/ source for every supported agent CLI.

• Swarm queue + cost telemetry (CLI)live

  swarm status and add read and write the task queue, and cost telemetry ships in the published CLI bundle (swarm_cost.py).

• Per-CLI authority matrix scaffolded by initlive

  init writes agent-authority.yaml into your repo from the bundled template — diffable YAML you own, shipped in CLI 4.5.0+.

Works with a caveat: repo-checkout only, partial wiring, or a deferred sub-part. The gap is named, not hidden.

• Swarm run / pick / quality orchestrationbeta

  Repo-checkout only. The orchestrator modules are not yet in the published bundle, so CLI-installed users get queue read/write and cost telemetry; full run/pick/quality needs a repository checkout.

• Telegram SEND auto-dispatchbeta

  The deferred responder relays finished swarm-run artifacts and auto-dispatches for linked owners; it runs on a per-tick pass rather than a standing service, so treat continuous auto-dispatch as not yet guaranteed.

• Cross-host provider profile syncbeta

  Provider profiles and per-owner bindings sync across hosts with no secret values on the wire. Cross-host secret distribution stays on the existing per-host channel; the sealed-envelope path is deferred.

On the roadmap, not operable yet. Listed so the bill never gets ahead of the build.

• Telegram linking, OIDC, and task intakeplanned

  Code ships, the surface is not available: Telegram is unconfigured in production. /v1/auth/providers reports telegram_oidc configured=false (the OIDC nonce endpoint answers 404 "not configured"), and the ingress bot's token was revoked upstream on 2026-10-05, so getMe is 401. Marked planned rather than live because the badge here means usable today — the same rule the pricing page states about itself.

• Telegram secret-write confirm flowplanned

  Code ships, the surface is not available: Telegram is unconfigured in production. /v1/auth/providers reports telegram_oidc configured=false (the OIDC nonce endpoint answers 404 "not configured"), and the ingress bot's token was revoked upstream on 2026-10-05, so getMe is 401. Marked planned rather than live because the badge here means usable today — the same rule the pricing page states about itself.

• Team bulk-provisionplanned

  A single team-provision command (and a committed team license) so clone + init inherits team config without a per-developer sign-in is planned.

• Release provenance + signature verificationplanned

  The installer verifies the bundle's SHA-256 checksum, not a signature. Published provenance plus a verify step (and a 0dai verify command) is planned; until then, do not assume a signature check at install time.