What's live today — and what isn't yet

Tier 1 — live and working

• One daemon + CLI over every adapter

  agentproto <verb> — auth, daemon, install, run, chat, sessions, serve, tunnel, browser, mcp-bridge, onboard, cron, pack and more. Nine adapters ship today (Claude Code, Claude SDK with Anthropic/Moonshot/OpenRouter gateway modes, Codex, Hermes, opencode, Mastra Code + in-process, Mastra Agent, OpenClaw, browser-as-agent), each self-declaring its models and modes via an AIP-45 manifest.

• Uniform agent lifecycle

  Spawn, prompt, tail output, export a full conversation to markdown, kill, list — the same verbs whether the CLI underneath is Claude Code or Hermes. Session descriptors carry pid, liveness, cost and token usage.

• Durable policy gates

  Attach a completion gate (shell command or LLM judge) to a session's turn-end. policy:passed / policy:failed fire on an event bus; a commit can be staged behind the gate and wait for an explicit human ack. Survives with no client attached.

• Nested orchestration with role gating

  Any spawned agent can become a scoped orchestrator with its own sub-gateway to spawn and supervise children — executor roles cannot delegate, supervisor roles can, with depth and children caps enforced by the daemon.

• Fan-in monitoring

  One long-poll call blocks until any of N watched sessions fires a lifecycle event — orchestration over many agents without an N-way polling loop. Scriptable from REST, MCP, or `agentproto sessions wait`.

• Workflows, routines, and cron

  WorkflowRunner executes ordered stages of concurrent steps with explicit barriers, session reuse across stages, output-schema validation with retries, and per-run cost ceilings. A durable cron scheduler lives on the daemon.

• MCP composition

  The daemon is itself an MCP server (~90 tools), and any spawned agent can mount external MCP servers at spawn time — including the daemon's own orchestration gateway, scoped.

• Terminals, browsers, tunnels, packs

  PTY sessions, a stealth browser as an agent target, Cloudflare tunnels to expose a local daemon over HTTPS, and installable skill packs (`agentproto pack skill` / `install skill/<slug>`).

Tier 2 — the AIP spec family (roadmap)

The repo carries ~52 numbered AIP specs. Beyond the ones backing Tier 1, most reference-implementation packages are 0.1.0-alpha scaffolding — schemas and intent, with build/validate bodies still to be written. They are an open standard being implemented in public, not shipped capability. If you find a Tier 2 claim anywhere that reads as shipped, file an issue — this split is the contract.