/inbox: one list with two tabs, Needs you, everything waiting on a person, and Running, everything in flight. It opens in the thread view. /inbox?tab=running opens it on Running, and /inbox?brands=all on every brand.
- Rows waiting on you, and outreach emails waiting to be sent, are under Needs you.
- Work that is approved and moving is under Running, together with the runs going on right now.
- What your own assistant filed is not a separate list: its open rows are in Needs you and its moving ones are in Running.
Needs you
Each row is one thing waiting on you: a sentence, the reason in a line under it, and at most three buttons. The order is:- A change that will ship on its own when its 48-hour window ends (“Ships Thu 09:00 unless you stop it”), soonest first. If nobody looks at it, it ships, so it leads.
- Everything else by how long it has waited, oldest first. A row that has waited a day or more says so: Waiting 3 days.
Decline from the queue records the reason as “not now”. To give a different reason, or a note the next draft should learn from, decline from the change’s own page.
Running
Runs come first, the ones waiting on your answer before the rest. Then comes work you already approved that is on its way or live.- A run has Stop. A run waiting on you also has Answer, which opens it in the panel with a link to its thread, where you answer.
- A change that is live has Undo while its 30-day way back is open. Undo works the same way as on the change’s own review page.
- A change inside its 48-hour window has Stop here too.
One brand or all brands
The queue shows the brand the switcher is on. With more than one brand in your organization, All brands shows every brand at once, grouped by brand. The brands follow the queue’s own order: the brand with the row that comes first in the queue leads, and each group keeps that order. If one brand’s rows can’t be read, the queue says which brand and leaves it out of the counts. It never shows that brand as having nothing waiting.The panel beside the list
Click a row, or press Enter on it, to open it in the panel on the right. The panel shows what the row changes and why, the draft itself, and every action it has. A change that can’t be undone once it ships says so here, before the Approve button. The panel stays on the row you picked until you pick another one or switch to another tab yourself. Edit on an article, a post or a rewrite opens the draft in the panel. Change it, then press Approve with your edit. Any other change is edited section by section on its own review page, and Edit opens that page. On a screen narrower than 1024 pixels there is no room beside the list. The same panel opens full screen instead, with Back to the queue at the top. It works for every brand’s rows, including on All brands. Where a row has a page of its own (a change’s review, a run’s thread), the panel links to it.When an action doesn’t go through
A row leaves the list as soon as you act on it, and the queue says what happened in one line, for example Approved “Rewrite the pricing page”.- It failed. The row comes back in the same place with the reason in our words and Retry. In the panel, every other action stays available too, so you can change your mind. Nothing disappears without a line saying where it went.
- Someone already answered it in Slack, by email, over MCP or in another tab. The row stays gone and the line says so, for example “Already approved by a member of your workspace”. There is nothing to retry.
- Your stop arrived after it shipped. The row says “It shipped a moment before your stop.” and offers Undo instead of Retry.
Keys
The keys do nothing while you are typing in a field.
Staying current
While the page is open, the queue reads again within two seconds of any of these happening in your organization:- a new row or question for you
- a run finishing
- a change shipping, going live, or being taken back
From the command palette
Press ⌘K (Ctrl-K on Windows and Linux) on any page to open the command palette. Each time it opens, it reads the queue for the brand the switcher is on, and lists these at the top, under Queue:
Each one names the row it will act on, for example Approve next: “Rewrite the pricing page”, and its brand. A command with nothing to act on is not listed at all: with no run going there is no Stop, and if the queue can’t be read none of them are listed. What happened comes back in one line, as in the queue: for example Approved “Rewrite the pricing page”., the reason when it failed, or that someone already answered it somewhere else. If a stop arrives after the change shipped, the line says so; undo it from the queue.
To move to another brand, type its name or “switch” into the palette and pick Switch to that brand. It opens Today for that brand, as the switcher does. With one brand there is nothing to switch to, so nothing is listed.
Nothing in the palette raises an autonomy level or a budget.
Over MCP and the API
The queue has no powers of its own. Every action on it is theact verb on the same row (approve, decline, edit, answer, undo or stop), the same verb MCP’s act tool calls.
The list is GET /v1/queue. It returns, for every brand:
- the rows waiting on a person, oldest first
- the live sessions, the ones waiting on you first
project_id, and the response has a count per brand.
Done on something only you can do is the Inbox’s resolve, POST /v1/inbox/tasks/{id}/resolve. act does not cover it yet.