[DOCS] `claude agents` crashes opening a stopped session whose conversation is already open in another session; agent view version history stops at v2.1.202

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

The "Version history" table at the bottom of agent-view.md (currently the latest row is v2.1.202), and the surrounding "Attach to a session" / "Read session state" sections that describe opening a stopped session without acknowledging that another terminal may already have that conversation attached.

Current Documentation

From the Version history table at the bottom of agent-view.md (the current latest row):

| v2.1.202 | {/ min-version: 2.1.202 /}A name set with /rename or Ctrl+R on a background session persists when the supervisor stops and restarts its process, instead of reverting to the name the session was dispatched with. |

Nothing below that row.

From the "Attach to a session" section above the table:

Press Enter or → on a selected row to attach. Agent view is replaced by the full interactive session. When you attach, Claude posts a short recap of what happened while you were away. While attached, the session behaves like any other Claude Code session: every command, keyboard shortcut, and feature works. Attached sessions always render in fullscreen mode, regardless of your tui setting, because a background session has no terminal scrollback to append to.

From "Read session state", describing the stopped/process-exited row icon:

| ∙ | The process has exited. You can still peek, reply, or attach, and Claude restarts from where it left off |

The paragraph under "The supervisor process" that describes stopped/process-exited sessions:

Once a session finishes and sits unattached for about an hour, the supervisor stops its process to free resources. A session you have pinned with Ctrl+T is exempt and keeps its process running while idle. The transcript and state stay on disk either way, and the next time you attach, peek, or reply to a stopped session, the supervisor starts a fresh process from where it left off.

What's Wrong or Missing?

A. The v2.1.203 fix is not in the version history table

The v2.1.203 changelog records:

Fixed the agent list crashing when opening a stopped session whose conversation was already open in another session

The version history table currently ends at v2.1.202. There is no row for v2.1.203, so a user upgrading from v2.1.202 to v2.1.203 has no way to learn that the agent list crash — when opening a stopped session whose conversation is already attached in another terminal — was addressed in this version. The version history table is the canonical changelog reference for agent-view.md, and earlier rows in the same table miss comparable fix entries (for example, v2.1.199 had an agent_view-related behavior change that never made it into this table).

B. The "Attach to a session" section never acknowledges the multi-window / multi-attached scenario

Before v2.1.203, opening a stopped session from claude agents while that session's conversation was already attached in another terminal (for example, a claude attach <id> from the shell, or a peek-panel session opened in a second claude agents window) crashed the agent list. The "Attach to a session" section, the stopped/process-exited row description, and the stopped-session lifecycle paragraph all describe a single-attach model and never mention the multi-attach case. After the fix, opening a stopped session in a second viewer no longer crashes; the docs should make this explicit so users do not avoid attaching in a second terminal, and so users on earlier versions can recognize the fix when they see it in the changelog.

C. The 'v2.1.203' row needs to follow the existing {/* min-version: 2.1.203 */} prose convention

The other Version history rows wrap their note in {/* min-version: <version> */} so the inline version gates render on the live page. A new v2.1.203 row should follow the same convention so the prose is gated correctly on the public site.

Suggested Improvement

Option A: Comprehensive fix

Add a v2.1.203 row at the top of the Version history table:

| v2.1.203 | {/ min-version: 2.1.203 /}Opening a stopped session from claude agents no longer crashes the agent list when that session's conversation is already attached in another terminal (a second claude agents window or a claude attach <id> from the shell). Requires Claude Code v2.1.203 or later. |

And add a sentence to "Attach to a session" or to the stopped-session paragraph:

{/ min-version: 2.1.203 /}As of v2.1.203, opening a stopped session from claude agents is safe even if that session's conversation is already attached in another terminal; earlier versions could crash the agent list in that scenario.

Option B: Minimum fix

Add only the v2.1.203 row to the Version history table. The changelog will then show the fix when users compare versions, even though the in-body prose remains single-attach-focused.

Either option removes the gap that lets v2.1.202 → v2.1.203 upgrade users miss the crash fix entirely.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/agent-view#version-history | 654 (table top) | Version history table top entry is v2.1.202; v2.1.203 row missing |
| https://code.claude.com/docs/en/agent-view#attach-to-a-session | 177-199 | "Attach to a session" section never describes multi-window/multi-attach behavior |
| https://code.claude.com/docs/en/agent-view | 138 | "When you open a session that has stopped responding" paragraph covers single-attach flow only |
| https://code.claude.com/docs/en/agent-view | 125 | Stopped/process-exited row icon description treats attach as a single-attach operation |

Total scope: 1 page affected (4 reference points on it).

Similar fix entries already documented in the Version history table (as precedent for the prose style):

| v2.1.195 | {/ min-version: 2.1.195 /}In-flight work carries over when you background a session on Windows too; set CLAUDE_DISABLE_ADOPT=1 to stop it instead. The Completed group fills the remaining vertical space and the header compacts on short terminals. An older Claude Code version no longer drops newer sessions' state.json fields or hides those sessions from claude agents. Attaching to a stopped session switches immediately instead of showing a blank screen for up to five seconds. A supervisor that can't accept connections exits and releases its lock on its own. |

| v2.1.202 | {/ min-version: 2.1.202 /}A name set with /rename or Ctrl+R on a background session persists when the supervisor stops and restarts its process, instead of reverting to the name the session was dispatched with. |

Related prior art (multi-window / multi-attach fixes that were documented in the changelog but never added to the Version history table):

Fixed claude agents: pressing back in one window no longer detaches other windows attached to the same session

This v2.1.176 changelog entry is the closest sibling — a multi-window scenario fixed in the agent list that was never surfaced in the Version history table. The same gap exists for v2.1.203.