Project overview
The home of a project — its sandboxes, stages, and health in one place.
Every project has an Overview: a single screen that answers "what is in this thing?" without opening a sandbox or reading a line of code.
It's an inventory, not a dashboard. Each kind of piece your app is built from gets a count you can click into.
Annotated screenshot of the project Overview: a grid of tiles reading Functions 34, HTTP Routes 21, Workflows 4, Agents 2, Schedulers 3, Queues 2, Channels 1, Emails 6, MCP Tools 5, CLI Commands 2, Gateways 1. Callout: "Everything your app is made of, counted."
What's counted
- Functions — the units of logic everything else calls.
- HTTP routes and Channels — the ways the outside world reaches in, by request or by live connection.
- Workflows — multi-step processes chained together.
- Agents — the AI agents declared in your codebase.
- Schedulers and Queues — work that runs on a timer, and work that runs in the background.
- Emails — every transactional email your app can send.
- MCP tools and CLI commands — the ways other systems and assistants reach your app.
- Gateways — messaging channels like WhatsApp and Slack.
Overview, Weave, or Knowledge?
Three screens describe your app, and they answer different questions:
| Screen | Answers |
|---|---|
| Overview | How much of each thing is there? |
| The Weave | How is it connected? Every piece and what it references. |
| Knowledge | Why is it like that? The decisions behind it. |
Overview is the fastest of the three — it's the one to open when you're returning to a project and want your bearings back.
Where to go next
- The Weave — the same pieces, drawn as a connected picture.
- Stages & branches — where this project is deployed.