Handling review comments on your PRs
Screen PRs is for the PRs you review. My PRs is the other side: the open PRs you wrote, and the review comments waiting for you on them. From there you hand a comment to the agent session that owns the branch, or start a session on the PR when nobody does.
My PRs never posts anything to GitHub, and nothing reaches an agent until you tap it. A handed comment tells the agent not to post to GitHub and to reply in the session instead.
Open My PRs
Select My PRs in the sidebar, the fourth section (⌘4). SimpleEdit lists your open PRs with gh, so GitHub CLI must be installed and signed in. If it isn’t, the section says so, and refreshes once you select Refresh.
The list refreshes when you open the section, on Refresh, and every 5 minutes while a window is open.
What it lists
PRs that need action come first, each with a count. Select a PR to see its comments in three groups:
- Waiting for you, the comments that need action.
- Other open comments.
- A count of resolved threads.
A comment can be:
- an inline comment in an unresolved review thread, from you, your agents, other people or bots
- a review’s summary text
- a comment in the PR’s conversation
Status bots re-edit one sticky comment on every push, so a bot’s conversation comment is shown but never counted.
If a PR’s repository isn’t cloned on your computer, the PR says “Not cloned here” and you can’t hand its comments to a session.
What “needs action” means
A comment needs action when it is in an unresolved thread or at PR level, you haven’t handed it over or dismissed it, and:
- the model marks it, if you set up the model hint (see below); or
- it is new, if it has no mark. An inline comment is new when it came after the thread’s last hand-off or dismissal. A PR-level comment waits until you act on it, except an approving review’s summary, which is a thanks, not a request.
The counts count asks, not comments. A thread counts once however many replies it has. Each PR-level comment counts on its own. The sidebar, the list and a session’s “n asks” label all use the same count.
A reply from your agent in the thread doesn’t clear a comment. Handing it over or dismissing it does.
The model mark is a hint
If you set up a decision model, a comment that asks for a change gets the chip Asks for a change (model) and is listed first. For a PR-level comment, hover the chip to see which paragraph scored highest.
The mark only orders and labels. It never hides, dismisses or sends a comment. Unmarked comments stay visible under Other open comments. Without a decision model, you get no marks and the “it is new” rule. Everything else still works.
An edited comment loses its mark until the model has looked at it again.
Hand a comment to an agent
Each waiting comment has these actions:
- Hand to ‹session›. SimpleEdit finds the session that owns the PR’s branch and gives it the comment as a thread. A comment on a specific line is anchored to that line in the code as it was when the reviewer wrote it. A PR-level comment is anchored to the PR. The agent answers in the thread in its session.
- Dismiss, when the comment needs nothing.
- Open on GitHub.
The owner is, in order, a workflow worker that opened the PR, the session in the worktree whose branch is the PR’s branch (the active one, or the only live one), and a session you can resume. If several sessions qualify, you pick. Handing the same comment twice, from your desk and your phone, makes one thread.
Hand all marked (n) hands every marked, waiting comment at once. When some waiting comments have no mark, the button reads Hand all (n).
Start a session on the PR
When no session owns the branch, the comment shows Start a session on ‹branch›. SimpleEdit fetches the PR, creates a worktree on its head commit, starts a session there and hands the comment over. It works only for a repository open in the window you are using. If a local branch with that name already exists, SimpleEdit moves it forward to the PR’s head, leaves it alone when it is ahead, and stops when the two have diverged.
The Review Room shows the same chip and Hand to on comments on your own PRs. A session’s row shows “n asks” and opens My PRs at that PR.
On your phone
The phone has My PRs next to the PR board. It lists your PRs and their waiting comments with the chip, Hand to, Hand all marked and Dismiss. Start a session and the Review Room are desktop only, and the phone says so. Marks and hand-offs are shared with the desktop.
Calibrate the “asks for a change” question
The model reads each comment and answers one question: does it ask for a change to the code or the PR? A score above a threshold becomes a mark. How many comments ask for a change differs a lot between repositories and teams, so there is no built-in threshold. Until you calibrate, nothing is marked.
You calibrate with the agent that has your decision model set up, and you stay in control of the result:
- Ask your agent to calibrate the question for comments. It measures the question on comments from PRs you wrote in the last 180 days. This needs a decision model, and runs one at a time.
- When the run finishes, a card appears with up to 40 comments for each kind: inline comments, and PR-level text. Mark each one Asks for a change or Doesn’t ask. Skip a comment you can’t judge. The agent’s hint, such as “a later commit followed”, is not an answer and never fills a label.
- Each kind needs 15 of each answer before it can be applied. The card shows how well the fitted threshold agrees with your labels.
- Select Apply. A kind that doesn’t have enough labels is left out, and a threshold you already have for it stays.
The agent never supplies a threshold. SimpleEdit computes it from your labels. A new threshold takes effect at the next My PRs refresh.
A calibration belongs to one model and one wording of the question. If you change the model or reword the question in Settings, that kind stops marking until you calibrate again.