Needs you

Everything that waits on you in a project is in one place, Needs you, with one count. The count on the tab, the phone badge, the Overview and the page title is the same number, and it always matches the rows below it.

What counts

• open cards you may decide;
• stuck items that need a person;
• your own items that are ready to start or ready to close;
• items to sort, if you can edit the plan.

The top of the tab says how many things wait on you and how many of them hold up the milestone in Now (“8 things wait on you. 3 of them hold up 2.4.”). Those come first.

Six verbs

Verb	What it holds	Example (Dictly)	You…
Decide	Plans and brief edits	“Add milestone 2.5 Offline, due Dec 15”; “Not doing · added Android in 2026”	Approve, or send it back with a note
Answer	Questions and stuck work	“Which languages first?”; “DIC-145: Xcode needs an Apple ID”	Pick an option or write an answer; retry or unblock
Review	Screenshots, reports, designs	“Pick the welcome screen”, two options	Pick one and approve it, set one aside, or request changes (Reviews and outputs)
Allow	Workers asking to do something	W-42 wants to run a command outside its sandbox	Allow, Allow for this run, Deny
Do	Your own items	“DIC-137 Record the demo video”	Do it, then Mark done
Sort	Things captured without a place in the plan	“Haptic tick on start”	Give it a place and Accept (Triage)

Allow cards

When a run hits a permission prompt in its CLI (it depends on the profile’s access mode), the prompt becomes an Allow card while the run waits. The card names the action and the item it serves.

• Allow lets this one request through.
• Allow for this run lets the same request through for the rest of the run. It is offered for MCP tools, and for Codex commands where Codex supports it.
• Always allow <prefix> appears for Codex commands when Codex itself proposes a command prefix. It adds a rule to that Codex home’s own rules on that runner: matching commands then run outside the sandbox without asking, in Minga’s runs and in your own Codex sessions on that home. See Codex auto-review.
• Deny refuses it. The run goes on without it, or stops if it cannot.

Who may decide a card

A card is sent to one person: the approver its agent named, or the person accountable for the item. That person, and a workspace owner or admin, may decide it. A permission prompt is decided only by the person whose run it is.

Planned Anyone in the project may decide any card, labelled “for Becky”, with Becky getting a note.

After you decide

A decided card folds away. It is not lost: a decided card is a decision record, and the Overview lists it under Decisions. Lea hears your decision in her next turn.

From your terminal

Over MCP, needs_me lists what waits on you across your projects, and answer answers a plain question (one whose options change nothing in the plan and that holds up no item). Everything else (plans, permissions, reviews, outward actions, questions that hold work) comes back with a link to answer it in the app.