All guides

Handling review comments on your PRs

My PRs lists your open PRs and the review comments waiting on them. One button hands a comment to the agent session that owns the branch, or starts a session on the PR. Nothing reaches an agent until you tap it, and My PRs never posts to GitHub. A handed comment tells the agent to reply in the session, not on GitHub.

Open My PRs

Select My PRs in the sidebar, the third section (⌘3). It uses gh, so GitHub CLI must be installed and signed in; if not, the section says so until you select ↻ (Refresh) in the section header. The list refreshes when you open the section, on ↻, and every 5 minutes while a window is open.

What it lists

PRs are grouped into Approved, then Today, This month and Older, most recently updated first. A PR that needs action shows how many comments wait on you. The sidebar header shows one amber number: the PRs waiting on you, either because they have asks or because they are approved and ready to merge. The My PRs header says how many are approved and how many asks wait, and an approved PR’s detail reads ”✓ Approved by ‹names›”. Pick a repository under Repo to filter.

Select a PR to see its comments in these groups:

On desktop, every PR also has a session control: Open session: ‹label›, Open session… to pick when several are live, or New session on ‹branch›. The phone has none.

A comment is an inline comment in an unresolved thread (from anyone, bots included), a review’s summary text, or a comment in the PR’s conversation. If the repository isn’t cloned on your computer, the PR never leaves you stuck: Locate clone… lets you pick the folder (desktop only), Open on GitHub opens the PR, and while another session is live you can hand its comments to that 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 either:

These never count as asks, but still show under Other open comments:

Counts are asks: a thread counts once however many replies it has, and each PR-level comment counts on its own. The sidebar, the list and a session’s “n asks” label share one count. An agent’s reply in the thread doesn’t clear a comment; handing it over or dismissing it does.

The model mark is a hint

With a decision model set up, 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. Without a decision model there are no marks and the “it is new” rule applies. An edited comment loses its mark until the model rereads it.

Hand a comment to an agent

Each waiting comment has:

The Review Room shows the same chip and Hand to on comments on your own PRs, and a session’s row shows “n asks” and opens My PRs at that PR.

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); a session you can resume, marked (restorable). The button’s menu lists every session in that worktree, and New session on ‹branch›. If several are live and none is active, the button reads Hand to… and only opens the menu.

To hand every waiting comment at once, use the button above them: Hand both to ‹session› or Hand all to ‹session›. Its menu is Hand all (n) to and also has Hand only the n marked.

Each comment reaches the agent once: handing it twice, from desktop and phone, makes one thread, and handing it while its thread is open sends nothing. Once the thread is resolved, handing it again reopens it. If the session ends and no other takes over, the comment goes back to Waiting on you.

Start a session on the PR

When no session owns the branch, the button reads New session on ‹branch›; otherwise it is in the button’s menu. SimpleEdit fetches the PR, creates a worktree on its head commit, starts a session there and hands the comments over. Claude Code gets them in its first prompt, and Codex usually does too. OpenCode gets them after its first turn. It works only for a repository open in the window you are using. If a local branch with that name exists, SimpleEdit moves it forward to the PR’s head, leaves it alone when it is ahead, and stops when the two have diverged.

On your phone

The phone has My PRs next to the PR board, with the chip, Hand to and Dismiss. New sessions and the Review Room are desktop only: with no session on the branch, it says “No session on ‹branch› yet. Start one on the desktop.” Marks and hand-offs are shared with the desktop.

Calibrate the “asks for a change” question

The model scores each comment on one question: does it ask for a change to the code or the PR? A score above a threshold becomes a mark. There is no built-in threshold, so until you calibrate nothing is marked.

  1. Ask the agent that has your decision model set up to calibrate the question for comments. It uses comments from PRs you wrote in the last 180 days, and runs one at a time.
  2. When the run finishes, a card shows up to 40 comments per kind (inline comments, and PR-level text). Mark each Asks for a change or Doesn’t ask, or skip one you can’t judge. The agent’s hint, such as “a later commit followed”, never fills a label.
  3. Each kind needs 15 of each answer before it can be applied. The card shows how well the fitted threshold agrees with your labels.
  4. Select Apply. A kind without enough labels is left out, and a threshold you already have for it stays.

SimpleEdit computes the threshold from your labels; the agent never supplies one. It takes effect at the next My PRs refresh. A calibration belongs to one model and one wording of the question: change either in Settings and that kind stops marking until you calibrate again.