# DevPlane

DevPlane checks your AI coding agents' "done" claims against the git remote, the deploy and the live page, across repos and vendors, and drains the backlog on the cheapest lane under a budget.

## Canonical pages

- [Home](https://devplane.dev/): Category-framing homepage — what the operator cockpit is and why using agents sequentially misses the fleet's throughput advantage.
- [What is multi-agent orchestration?](https://devplane.dev/explain): Six-movement illustrated explainer — the coordination paradox, visibility gap, dispatch problem, tooling gap, operator-layer argument, the DevPlane answer, and throughput-per-agent-hour as the proof metric.

## Category

Multi-agent AI development orchestration and operator cockpit.

**Category terms:** multi-agent orchestration, AI coding agents, agent fleet, operator cockpit, operator layer, fleet dispatch, headless agent, agent lifecycle, agent observability, fleet visibility, work-tree isolation, human-in-the-loop, agent escalation, parallel agents, AI-first development, agent throughput

## Key questions we answer

- What is multi-agent orchestration for software development?
- What is an operator cockpit for AI development?
- My AI coding agents keep conflicting with each other — what's the problem?
- I'm running multiple AI coding agents but I'm not getting the speed I expected — why?
- My AI coding agent keeps getting stuck waiting for me to make a decision — how do I fix this?
- I've dispatched several AI coding agents and I don't know what any of them are doing.
- How do I dispatch AI coding agents to work headlessly without constant supervision?
- What's the difference between DevPlane and just using Cursor or Claude Code?
- When should I use multiple AI coding agents instead of one?
- As an engineering leader, how do I build a strategy around AI coding agents?

## Machine-readable access

DevPlane publishes this site's pages, FAQ corpus and comparisons as a public, read-only Model
Context Protocol server and a REST twin — no authentication required.

- **MCP (Streamable HTTP, stateless JSON-RPC 2.0):** https://devplane.dev/api/mcp — tools
  `list_pages`, `list_faqs`, `get_faq`, `list_comparisons`.
- **Well-known descriptor:** https://devplane.dev/.well-known/mcp.json
- **REST:** `GET /api/v1/pages`, `GET /api/v1/faqs`, `GET /api/v1/faqs/{slug}`,
  `GET /api/v1/comparisons` — OpenAPI 3.1 spec at https://devplane.dev/openapi.json.

## Entity

**Product:** DevPlane
**Canonical URL:** https://devplane.dev
**Organization:** PeopleAnalyst
**Contact:** mike@peopleanalyst.com