Issues and pull requests / Issues
See what runs on an issue or a pull request
An agent or screening can work on an issue or a pull request now, so it can change in a minute. A blue badge next to the title shows what runs on it, so that you know before you act.
3 min read
1. Find the badge
Open the issues list or the pull requests list. The badge shows on each row that has work in progress. No badge means that nothing runs on the item now.
| The badge says | What it means |
|---|---|
| Screening | Screening reads the item. Until it ends, only the author and the maintainers see the item. |
| Triage running | One agent runs on the item. The badge gives the name of the agent. |
| Triage waiting | One agent is in the queue and has not started. |
| 2 agents running | Two or more agents are on the item, and at least one of them runs. With no agent that runs, it says 2 agents waiting. |
2. See each agent
Hold the pointer on a badge. The tooltip lists each agent with Running or Waiting.
3. Open the item
Open the item. The same badge shows in the header, next to the state. Click the badge:
- The page goes to the Factory panel, or to the screening notice while screening reads the item.
- On a pull request, the badge opens the Agents tab of the right column, which holds the Factory panel.
The badge updates by itself when a run is added, starts or ends. While screening reads an item, its page updates by itself until screening ends, for up to 30 minutes.
4. Check the held queue
If you are a maintainer, the list header also shows the held queue:
- 3 screening: the items, comments and Community posts that screening still reads.
- 2 held for review: the ones that screening holds for a maintainer.
Each one opens the Held for review page. If screening does not end in about 30 minutes, it holds the item for a maintainer to decide.
Note
An item in screening or held for review has no agent runs. The factory waits until the item shows to everyone. The images and videos attached to text in screening stay hidden until the text shows. See Attachments from people without write access.
Done
A blue badge shows which items are in screening, and which have an agent that runs or waits. No badge means that you can act now.
Later: src, REST and MCP
In a terminal, run:
src issue view 12 --json activity
src pr view 7 --json activity
src pr list --json number,title,activity
screeningistruewhile screening reads the item.runslists each run that is queued or running, with itsagentand itsstatus(queuedorrunning).- An empty
runslist andscreening: falsemean that nothing runs on the item now.
REST and MCP give the same data. The REST paths are under /api/v1/repos/{owner}/{repo}.
| You want to | REST | MCP tool |
|---|---|---|
| See what runs on one item | GET /issues/{n}/activity, or GET /pulls/{n}/activity | get_item_activity |
| See what runs on all items | GET /activity | list_item_activity |
GET /issues/{n}/activityanswers{ "screening", "runs" }. Each run hasrunId,agent,status,createdAtandstartedAt. A person or a token that cannot read the item gets 404.GET /activityanswers{ "runs", "held" }. Each run has thenumberof its item,agentandstatus.heldhas the countsscreeningandquarantined, and they are 0 for people who are not maintainers.
Use the REST API has the other routes.