You only see actions you have permission to take. If an action is missing, ask a project editor or admin.
The groups
Items are grouped by kind, with approvals first.
Each item shows a title, a detail line, and sometimes an impact line, with its buttons on the right.
1
Open Needs you
Click Needs you in the Agent group of the sidebar. Home shows the top three; click All to see the rest.
2
Read the item
The detail line says what the agent saw. Use the item’s button to open the related page if you want more context.
3
Decide
For an approval, click Approve or Reject. Both open a confirmation, and a rejection asks for your reason. Other items have their own button: Mark as applied or See details for a cost saving, Open the issue for an issue, Review the guardrail or Create a guardrail for a guardrail. Mark as applied records the recommendation as applied; it does not change your configuration.
Item types and lanes
With the new agent layout on, Needs you sorts every item by what you can do with it. The lanes sit on the left and the selected item opens as a card on the right. The filters above the lanes show how many items each one holds. If I could not read part of the queue, the filters and lane headings show no numbers. When the list is cut, the numbers are shown with a ”+” (for example “5+”), because there may be more.
Whether you may decide an item is checked on the server, not only in the page. If you lack the permission, the item moves to FYI as waiting on an admin; it does not show a button that would fail.
A tool approval shows how long it has left, as “expires in 28 min”, “expires in 2 h” or “expired”. Approve and Reject open the same confirmation as before. Any other action on an item stays available as a secondary button, such as opening the related page.
When you finish an action, focus moves to a line that says what was done. Nothing on the page announces changes on its own.
Tool approvals are in the app and in the daily digest only. They are for owners and admins, and they are not sent to chat.
Deciding in place
With the new agent layout on, a Decide item has its own primary button on the card, so you can act without leaving Needs you. You only see the button when you hold the permission the change needs; the server checks it again when you press it. If it refuses (a plan limit, a missing permission), the card shows the server’s message and stays where it is.
When an apply goes through, the card turns into an Applied line that says what was done, and the list, the sidebar count and Home update together. An apply is a change, not proof that it worked: the line never says a problem is fixed. With fix tracking on, an applied card about an issue also shows the state of the fix it started, in Zespan’s own words and with its numbers (for example “Measuring · 3 of 200 runs”). See the fix path for the states. If the state cannot be read, the card says so and offers Retry.
Turning on a guardrail or an alert is recorded in the Audit log. These changes do not appear in Activity yet.
Draft an alert from an issue
With the new agent layout on, an issue page has a Draft an alert button when the issue has a metric an alert can watch. It shows the rule it would save (the metric, the threshold and the window) and a 30-day backtest, for example “Would have fired 3 times in the last 30 days”. Opening the draft saves nothing: the rule is created only when you press Turn on. If the last 30 days cannot show the rule would have caught the issue, the draft says why and offers no button. Alerts need the Pro plan.Drafts from an agent run
When runs are available for the project, a run can leave drafts here. A drafted alert is a Decide item for people who can manage alerts; for everyone else it waits on an admin. Its Review alert button opens the same Draft an alert dialog as the issue page, so you read the rule and its 30-day backtest and press Turn on only if you want it. Closing the dialog returns focus to the button, or to the page heading if the item has left the list. A run that stopped before it could check everything marks its drafts as partial. The card says so in its Not checked line, for example “Partial · cause not confirmed · 3 of 5 sample runs read”. Read that line before you act on the draft.Code fix drafts
When a run drafts a code fix, it is a Decide item for people who can manage alerts, titled like “I drafted a code fix fortool.x.” The button is Review the fix. It opens the issue’s fix path, where you read the suggestion, change your code, and mark the fix as shipped. It is a link, not an approval: I do not change your code myself, and the card never says Approve. For everyone else the item waits on an admin. When the same issue also has a suggested fix to apply, you see one item, not two.
When three or more tool approvals expire unanswered within a week, one FYI says so and suggests a confirm-first policy or a longer wait. Neither counts in the badge.
I try first, then ask
When investigations are on for the project, I investigate an issue whose cause is unclear before I ask you to label runs. This happens within your run limits: it uses the same daily limits as other automatic investigations, and it waits when a limit is reached. While I am trying, the label ask is hidden, so you are not asked for something I may settle myself. If I could not try, or could not settle the cause, the ask shows with one line that says why:
Each line ends with “Your labels on a few sample runs settle it.” If I could not read part of this, the ask shows as it always did, with no claim that I tried.
Label asks come last. In the queue they sit after every decision, and on Home the batch titled “I need your labels on 2 issues.” is shown after the others and is the first to drop when there are more than three groups. The headline names a decision before it names a label ask.
Model tests
When a model you call is about to retire and it names a successor, I can test the successor on your own calls first. Two cards belong to this.
A result is checks passed on a small sample. It is not an accuracy figure. See Test the successor.
Fixes I drafted on my own
When an issue is proven, I can draft its guardrail myself, without waiting for a person. It lands here as the same Decide card as any guardrail draft (“I drafted 1 guardrail for you to decide.”), with the line “It would have stopped 9 of 14 failing runs in the replay.” when I have the numbers. The draft says “Drafted by Zespan at” with the time. I only draft: applying it stays yours, and pressing Turn on guardrail turns it on in dryrun first. A fix I drafted shows in Done for you once, and is left out there while its card here shows the same numbers. See Drafted by Zespan.Version regressions and agents I cannot stop
With the new agent layout on, three kinds of card are about one of your agents. On Home they share one group, “I need you to look at 2 of your agents.”
A tied drop is said once: here, or in the Agents row on Home when this card is not shown. Someone who cannot deploy prompts sees the plain card without the Roll back button.
Answer items
With the new agent layout on, an Answer item is a question Zespan cannot settle from your traces. You answer it on the card, without leaving Needs you. You only see the controls when you hold the permission to answer; otherwise the item waits on an admin and is read-only.
One press sends one request. After the answer, one line stays on the card and keyboard focus moves to it, even after the item leaves the list. It repeats what the server returned: Saved. The Payments pack is now on. (a pack is named only when it changed), or Saved. No pack changed: packs are picked once enough tool calls arrive. For a queue, Opened a queue with 3 sample runs. or Opened the existing queue. An Open the queue link goes to it. If the request fails, the card says Couldn’t save your answer. Nothing changed. Try again. (or Couldn’t open the queue…) and keeps the buttons.
If a refresh of the list fails after you answer, the page stays with a note and Retry, and the outcome line keeps focus. On Home, a queue question links to Annotation queues, where the button is.
The same tool and field questions are on Detector packs, and the queue question on Annotation queues.
Next steps
- Home: the top three items live here too
- Activity: see what happened after you decided
- Agent runs: the investigations that leave drafts here, and that try first before asking for labels
- Notifications: the daily digest of what waits here, by email or chat
- Detector packs: where tool and field questions are answered in full
- Model lifecycle: test a successor model on your own calls
- Guardrails: the fixes I draft on my own
- Agents: targets, the daily stop, versions and the rollback card
- Issues, Guardrails, Costs: the pages behind each group
- ZespanPilot: where approvals begin

