[DOCS] Agent view "Pull request status" only describes sessions opening a PR; v2.1.205 also links existing PRs that a session edits, merges, comments on, or pushes to

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/agent-view

Section/Topic

• The "Pull request status" subsection under "Monitor sessions with agent view" (currently around line 148 of agent-view.md), specifically the opening sentence that frames the row's #N label as the PR "the session opened".
• The Ready for review row in the "Organize the list" section (around line 205) that says a session moves into Ready for review "when it has an open pull request" without naming the new case where the open PR is one the session is acting on rather than one it opened.
• The Version history table at the bottom of agent-view.md, which currently stops at v2.1.203 and has no v2.1.205 row for the new link-to-existing-PR behavior.

Current Documentation

The "Pull request status" subsection in https://code.claude.com/docs/en/agent-view (around line 150) reads:

When a session opens a pull request, a #1234 label appears at the right edge of the row, linked to the pull request in terminals that support hyperlinks. The label persists when you send a follow-up to the session, so the pull request remains visible while the row reverts to live progress. Background sessions that isolated their changes in a worktree open these pull requests themselves; [How file edits are isolated](#how-file-edits-are-isolated) covers when that happens and what a session never does without asking. When a session has opened more than one pull request, the label shows a count instead, such as 3 PRs, colored by the open pull request that most needs attention. Open the [peek panel](#peek-and-reply) to see them all. The pull request number is colored by its status: | Color | Pull request status | | :----- | :-------------------------------------------- | | Yellow | Waiting on checks or review, or checks failed | | Green | Checks passed and no review is blocking | | Purple | Merged | | Grey | Draft or closed |

The "Organize the list" section then grounds the same understanding of the row:

Agent view groups sessions so the ones that need input are at the top, with Ready for review and Needs input above Working and Completed. These group names don't map one-to-one to the [states](#read-session-state) above: a session moves to Ready for review when it has an open pull request, and Completed collects finished, failed, and stopped sessions together.

The "Filter sessions" subsection, the "Dispatch new agents" subsection, and the "Version history" table at the bottom of the page never mention any behavior other than sessions opening a PR they created.

The Version history table at the bottom of agent-view.md currently stops at v2.1.203:

| v2.1.203 | {/ min-version: 2.1.203 /}A gateway ANTHROPIC_BASE_URL exported in the dispatching shell reaches the sessions dispatched from it into that same directory when the supervisor shares that gateway environment, instead of being dropped while the API key exported alongside it was kept. ... |

No row in the table mentions sessions linking to an existing PR, and there is no v2.1.205 row at all.

What's Wrong or Missing?

A. The "Pull request status" section frames the #N label as the PR the session opened

The v2.1.205 changelog entry says:

Improved agent view: sessions that edit, merge, comment on, or push to an existing PR now link it in claude agents

That widens the trigger for showing a row's #N label from "the session opens a pull request" to "the session edits, merges, comments on, or pushes to a pull request". After v2.1.205 a session that does not open any PR but instead addresses an existing one — for example, a session asked to address review feedback on a teammate's PR, run a /autofix-pr job, post a fix as a follow-up push, or merge a PR through gh pr merge — should now show that PR's #N label in the same place. The page still says the label is "the pull request the session opened", so a reader trying to understand why their session row shows #1234 when the session never created a pull request has no explanation.

B. The "Organize the list" description of Ready for review is similarly narrow

The Ready for review group description still ties the group membership to a PR the session has open, not to one it is acting on. A session that is editing an existing PR — for example, pushing follow-up commits, addressing review comments, or running the merge — should now also appear in Ready for review once v2.1.205 has linked the PR to the row, but the prose only describes the open-by-this-session case.

C. The Version history table has no v2.1.205 row for this change

The Version history table is the only place on the page where per-version changes are summarized. With no v2.1.205 row, a reader comparing v2.1.203 (the current top row) to the latest release cannot find the new edit/merge/comment/push behavior in the table and has no anchor pointing at the updated prose once it is added.

Suggested Improvement

Update the "Pull request status" subsection to reflect that the #N label covers both PRs the session opens and existing PRs the session acts on, add a matching note in "Organize the list", and add a v2.1.205 row to the Version history table.

Before (first paragraph of "Pull request status"):

When a session opens a pull request, a #1234 label appears at the right edge of the row, linked to the pull request in terminals that support hyperlinks. The label persists when you send a follow-up to the session, so the pull request remains visible while the row reverts to live progress. Background sessions that isolated their changes in a worktree open these pull requests themselves; [How file edits are isolated](#how-file-edits-are-isolated) covers when that happens and what a session never does without asking.

After:

A #1234 label appears at the right edge of a row when the session is linked to a pull request, either one it opened itself or an existing one it is acting on. The label is linked to the pull request in terminals that support hyperlinks. The label persists when you send a follow-up to the session, so the pull request remains visible while the row reverts to live progress. Background sessions that isolated their changes in a worktree open these pull requests themselves; [How file edits are isolated](#how-file-edits-are-isolated) covers when that happens and what a session never does without asking. {/ min-version: 2.1.205 /}As of v2.1.205, a session is linked to an existing pull request when it edits the PR's branch, merges the PR, comments on the PR (for example with gh pr review), or pushes new commits to the PR's branch. The #N label then appears on the row the same way it does for PRs the session opened, and the row moves into the Ready for review group under the same conditions.

Before ("Organize the list", the Ready for review description):

These group names don't map one-to-one to the [states](#read-session-state) above: a session moves to Ready for review when it has an open pull request, and Completed collects finished, failed, and stopped sessions together.

After:

These group names don't map one-to-one to the [states](#read-session-state) above: a session moves to Ready for review when its row is linked to an open pull request — whether the session opened that PR or is acting on an existing one (see [Pull request status](#pull-request-status)) — and Completed collects finished, failed, and stopped sessions together.

Before (Version history table currently stops at v2.1.203):

| v2.1.203 | {/ min-version: 2.1.203 /}A gateway ANTHROPIC_BASE_URL exported in the dispatching shell reaches the sessions dispatched from it into that same directory when the supervisor shares that gateway environment, instead of being dropped while the API key exported alongside it was kept. ... |

After (insert a new v2.1.205 row above the v2.1.203 row; everything else unchanged):

| v2.1.205 | {/ min-version: 2.1.205 /}A session that edits, merges, comments on, or pushes to an existing pull request is now linked to that PR in agent view: the row shows the PR's #N label and moves into the Ready for review group the same way it does for PRs the session opened. The peek panel lists the linked PR alongside any PRs the session opened. | | v2.1.203 | {/ min-version: 2.1.203 /}A gateway ANTHROPIC_BASE_URL exported in the dispatching shell reaches the sessions dispatched from it into that same directory when the supervisor shares that gateway environment, instead of being dropped while the API key exported alongside it was kept. ... |

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/agent-view | "Pull request status" subsection (opening sentence and the two follow-up paragraphs around the color table), the Ready for review description in "Organize the list", and the Version history table at the bottom of the page |

Total scope: 1 page affected.

The fix is in Claude Code v2.1.205. The widening of the PR-link trigger is most visible to users who run agents against an existing PR — for example, dispatching a session with claude --bg and a prompt that says "address review comments on PR 1234" or "merge PR 1234 once CI is green", or following up on an already-opened PR through /autofix-pr or repeated pushes. On v2.1.204 and earlier, those rows did not show a #N label and stayed outside Ready for review; on v2.1.205 they do, and the page should describe that. The existing per-version change list on the page (the Version history table) should grow a v2.1.205 row so the change is discoverable from the page itself instead of only the changelog.