Last updated July 5, 2026
App Boards & the Hub
A board becomes something more once you connect it to a repo. Give a board a governing Code Plugin source and it becomes an app board — one board, one repo, kept in sync both ways.
That changes what you see when you open it. A plain board opens straight on the canvas, because the diagram is all there is. An app board opens on its hub instead — a front page where the diagram is just one of six things you can check.
The six citizens
An app board tracks six things. Three flow in from your code, three flow back out to change it, and the diagram sits in the middle connecting them.
| Citizen | Direction | What it shows |
|---|---|---|
| Sources | In | The repo connection — branch, sync status, any reference docs |
| Aspects | In | Structure the plugin pulled from your code — database schema, API surface |
| Insights | In | What analysis and monitoring found — risks, opportunities, signals |
| Diagram | Middle | The map of nodes and edges everything else connects to |
| Intents | Out | The work queue — changes waiting for a developer to build |
| Skills | Out | The compiled skills bundle the repo pulls down |
The diagram doesn't lose its importance — it's still what every other citizen connects to. It just stops being the only door in. If three intents are waiting on your approval, you see that the moment the board opens, not after digging through the canvas.
The hub
The hub shows each citizen as a card: its current state, plus the one thing you're most likely to do next. The intents card comes first — you can review a draft and Lock & open it right there, without leaving the page. Every card links to its full view, and Open canvas is always one click away.
A hub only ever shows its own board. If a layer deep in your tree is an app board, drilling into it takes you to that layer's own hub — with that repo's own intents, aspects, and skills.
The command center
Your root board usually isn't an app board itself — it's the map of how your systems fit together, and its layers are where the app boards live. Open a root board like that and you land on the command center instead: one tile per app board, showing what needs attention (intents waiting on you, work in progress, sync status), plus totals across every app.
The command center only shows what's cross-cutting — it doesn't try to aggregate aspects or skills, since those only make sense inside one app at a time. It answers one question: across everything I'm building, what needs me today? Click a tile and you're on that app's hub.
Where you land
| You open | You land on |
|---|---|
| An app board (root or layer) | Its hub |
| A root board whose layers contain app boards | The command center |
| Any other board | The canvas |
Two things keep this predictable. Moving between layers from the canvas keeps you on the canvas — drilling into a node never bumps you to a hub mid-flow. And a shared link that captures a canvas moment (a viewport, a selected insight) always opens on the canvas, exactly as the sender saw it.
You can switch by hand any time: Open canvas from a hub, or the Hub button in the canvas toolbar.
One app, one repo — and no nesting
Two rules keep app boards unambiguous:
- One repo per app board. A board takes exactly one governing Code Plugin binding. The board is that repo's twin — two repos on one board would leave every intent and aspect pointing at the wrong place.
- No app boards inside app boards. An app board's layers model what's inside one repo, so they can't become app boards themselves. On a board inside an app board, the option to bind a governing source is replaced with a note pointing you at the app board above it. This is enforced automatically — you can't nest one by accident.
Becoming an app board
There's no setting to flip. Connect a repo through a governing Code Plugin source — usually by running /login from Cdx Code, or by binding one from the board's Sources panel — and the board becomes an app board immediately. You'll see a confirmation and land on its brand-new hub.
Disconnect the governing source and the board quietly goes back to being a plain board with just a canvas.