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. Fifteen agents install the same way (Claude Code, Claude SDK with Anthropic/Moonshot/OpenRouter gateway modes, Codex, Copilot CLI, Gemini, Grok CLI, Hermes, jcode, opencode, Mastra Code and its in-process variant, Mastra Agent, OpenClaw, pi, Antigravity), plus a browser adapter. Each declares its models and modes through an AIP-45 manifest.

• Uniform agent lifecycle

  Spawn, prompt, tail output, export a full conversation to markdown, kill and list sessions. The verbs stay the same 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 child-count caps enforced by the daemon.

• Fan-in monitoring

  One long-poll call blocks until any of N watched sessions fires a lifecycle event. Orchestrate many agents without an N-way polling loop, 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 with about 175 tools. Any spawned agent can mount external MCP servers at spawn time, including the daemon's scoped orchestration gateway.

• 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.