App Control Plane

0dai is the control plane for real coding agents. The app surfaces are designed to make sessions, worktrees, approvals, proofs, merge queue state, and rule health visible without turning 0dai into another IDE.

Product stance

  • Control plane, not another coding agent.
  • Runtime Broker before new UI writes.
  • Evidence before merge.
  • Rules and memory are product health, not hidden files.
  • Graph context becomes the long-term moat.

Market signals

  • Agent workspaces and worktree isolation are now table stakes.
  • Remote and mobile approvals are becoming normal user expectations.
  • Rules, memory, hooks, permissions, and review governance are moving into paid product surfaces.
  • The open gap is cross-agent delivery truth: ownership, proof, policy, and merge readiness.

Control-plane surfaces

Runtime control

Broker-mediated status and actions for live agent sessions, queues, blockers, approvals, and merge readiness.

Evidence and review

Proof, rule citations, CI state, reviewer notes, and deploy readiness in one operator cockpit.

Governance

Rules, memory health, approval policy, budget awareness, and merge queue status as product surfaces.

Delivery graph

Connected task, rule, decision, evidence, PR, CI, deploy, and outcome history for better routing.