When you sign in, you land on the Needs You inbox — the app’s home screen. It gathers, across every project, the things waiting on a decision from you and the runs working right now, so the first thing you see is what to do next.
The inbox is also where the old dashboard used to be. The home no longer shows a balance or spend — that moved to Usage. The home is now purely about attention.
This page explains what the inbox is and how to read it. For the wider tour of the interface around it — the icon rail, the breadcrumb bar, the command palette — start with Find your way around.
The header
The page is headed Needs You, with the line “Gates, approvals, questions and failures across your projects.” That sentence is the inbox in one breath: it spans all your projects, not just one.
Two actions sit at the top right:
- All projects — jumps to your full project list.
- New task — opens the command palette, the quick way to jump anywhere or start something. (The palette is a navigator, not a search of your content.)
The counts strip
Below the header, three counts give you the shape of your day at a glance:
- Needs you — how many items are waiting on a decision from you. When this is above zero it turns red, so a non-empty inbox reads as urgent.
- In flight — how many runs are working right now.
- Projects with activity — how many of your projects have something happening.
These are live tallies of the three groups below, nothing more — there’s no spend or trend figure here.
The three groups
The body splits into three groups. On a wide screen, Needs you and In flight stack in the main column on the left, and the By project rollup sits in a narrow rail on the right.
Needs you
The first group lists the items waiting on a human decision. Nothing here advances until you act. Each row is a link straight to the exact gate that needs you, so selecting one drops you onto the run where the decision lives.
Each item carries a label naming what kind of decision it is:
- Plan — a plan to approve before work begins.
- Question — a question the run asked; the row’s sub-line shows the question itself.
- Merge — a stage gate waiting for you to merge its pull request; the sub-line names the stage and the PR number.
- Failed — a run that failed and needs you to look; the sub-line summarizes the failure, or reads “Run failed” when there’s no detail.
You may also see Blueprint and Corpus items — a blueprint to approve, or a regression corpus draft to review — which work the same way: a label, a link to the gate, decide.
Each row shows the task title, the project name on a sub-line, and how long the item has been waiting (for example 3m ago or 2h ago). The list is ordered by kind first — questions come ahead of plans, plans ahead of merges, and merges ahead of failures — and within each kind the longest-waiting items float to the top, so what’s been stuck longest is hardest to miss.
In flight
The second group shows the runs actively working right now. These need nothing from you — they move on their own until they finish or reach a gate (at which point they appear in Needs you instead).
Each running run is a card you can open to watch it live. The card shows the task title, a running badge, and a live mini pipeline strip — a compact row of the run’s stages so you can see how far along it is at a glance. Below that, a sub-line reads the run’s branch followed by the current pipeline stage it’s working in, telling you where the work is happening right now.
By project
The right rail rolls the same attention items up By project, so you can see at a glance which projects are waiting on you, which are running, and which are clear. Each project is a row you can open, marked with a status dot:
- Needs you — something in this project is waiting on a decision.
- Running — the project has a run in flight.
- Paused — the project is paused.
- Clear — nothing needs you and nothing is running.
Alongside the dot you’ll see count badges — “2 needs you”, “1 running” — or a plain Clear when there’s neither. To move from this rollup into a project’s own pages, see The project sections.
It refreshes itself
You don’t reload the inbox. It refreshes on its own about once a minute, so new items appear and cleared ones drop off without you doing anything. To save work while you’re elsewhere, the refresh pauses whenever the tab is in the background and picks up again when you return to it.
When the inbox is empty — or won’t load
The inbox tells you plainly when there’s nothing to do:
- You’re all caught up — when nothing needs you and nothing is running. The message reads “Nothing needs you right now. We’ll bring anything that needs a decision back here.”
- Create your first project — before you have any projects, with a button to create one. “Spin up a project and DIJJI will start surfacing what needs you here.”
- We couldn’t load your inbox — if something goes wrong fetching it, with a Try again button to retry.
An empty inbox is the goal state, not a sign something’s missing — when You’re all caught up shows, every decision is made and every run is moving on its own.