[DOCS] `agent-view.md` version history omits v2.1.203 and no troubleshooting entry describes the macOS 15–20 second stall when opening or switching background sessions (regression fixed in 2.1.203, introduced in 2.1.196)

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

The "Version history" table at the bottom of agent-view.md (currently stops at v2.1.202) and the "Troubleshooting" section above it. The existing entry "A session fails before starting with a possibly low memory note" is a related surface but does not cover the v2.1.203 case.

Current Documentation

The current version history table ends at v2.1.202:

| Version | Change | | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 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. | | v2.1.200 | {/ min-version: 2.1.200 /}An older Claude Code version that rewrites the session list in roster.json preserves fields written by a newer version, matching the existing state.json guarantee, so sessions started by the newer version keep accepting input after the supervisor restarts. When you open a session that has stopped responding, the supervisor restarts its process and the session continues the interrupted response from where it left off. | | v2.1.199 | {/ min-version: 2.1.199 /}A background session whose process exits before it finishes starting on a low-memory host shows possibly low memory — free some up and retry in its row status instead of only the bare exit reason. Backgrounding a session with ← or /background carries its /color over to the new row. |

There is no row for v2.1.203. The corresponding "A session fails before starting with a possibly low memory note" troubleshooting entry only describes the v2.1.199 change to the row status text on actual low-memory hosts:

As of v2.1.199, when a background session's process exits before it finishes starting and the host is low on memory, the row's status names the exit and adds possibly low memory — free some up and retry. Earlier versions showed only the bare exit reason for this failure. The note is a hypothesis, not a confirmed cause. Claude Code adds it only when the process exited silently, without writing an error and without being stopped by a signal, and the host reported low memory at that moment. When the process did write an error before exiting, the row shows that error instead.

That troubleshooting entry addresses a process-exit failure on actually memory-starved hosts. The v2.1.203 regression is unrelated to the row status text: it is a 15–20 second stall on opening or switching sessions on macOS caused by a false low-memory signal in v2.1.196.

What's Wrong or Missing?

A. The version history table has no v2.1.203 row

The release notes for v2.1.203 state:

Fixed opening or switching background agent sessions on macOS stalling for 15–20 seconds due to a false low-memory detection (regression in 2.1.196)

The agent-view.md version history table lists v2.1.202, v2.1.200, v2.1.199, v2.1.198, v2.1.196, v2.1.195, v2.1.174, v2.1.172, v2.1.161, v2.1.157, v2.1.145, v2.1.143, v2.1.142, v2.1.141, and v2.1.139, but has no v2.1.203 row that records the macOS stall regression fix. The page's prose still says "If you are on an older Claude Code version, some behavior on this page may differ" and the table is the only place that tells a reader when the macOS stall regression was corrected.

B. The v2.1.196 row never mentioned the regression it introduced

The current v2.1.196 row lists the genuine additions shipped in v2.1.196 (single ← backgrounding, bypass-disclaimer display, default session names, handoff, .orphaned- suffix renames), but the docs never call out the regression it introduced. A reader cannot tell from the table that the 15–20 second macOS stall appeared in v2.1.196 and was corrected in v2.1.203, so users still on v2.1.196 through v2.1.202 have no in-page pointer to the workaround (update to v2.1.203 or later).

C. No troubleshooting entry matches the symptom

The macOS troubleshooting entries in this section cover Operation not permitted reading of protected folders and connect: no route to host on local-network targets. The "session is slow to respond after attaching" entry covers a different stall (attaching starts a fresh process and is briefly slow), not the 15–20 second pause on opening or switching sessions when the host is not memory-starved. A user experiencing the v2.1.196–v2.1.202 stall on macOS has no in-page troubleshooting entry to confirm the fix is in v2.1.203, what regressed, or whether their machine is genuinely low on memory.

Suggested Improvement

Option A: Comprehensive fix (preferred)

Append a v2.1.203 row to the version history table that records the regression, the symptom, and the fix:

| v2.1.203 | {/ min-version: 2.1.203 /}Opening or switching background agent sessions on macOS no longer stalls for 15–20 seconds when the host is not actually low on memory; the v2.1.196 false low-memory signal that gated session startup has been removed. The 15–20 second stall reappears only on v2.1.196 through v2.1.202. |

Optionally note on the existing v2.1.196 row that the release also introduced the false low-memory regression that v2.1.203 corrects, so users searching for the symptom can find the fix without scanning the table top-down.

Add a macOS troubleshooting entry next to the existing Background sessions can't read Desktop, Documents, or Downloads on macOS and Background sessions can't reach local-network hosts on macOS entries:

### Opening or switching a background session on macOS stalls for 15–20 seconds On Claude Code v2.1.196 through v2.1.202, opening a session from claude agents, attaching to a session, or switching between sessions on macOS could stall for 15–20 seconds because the supervisor was waiting on a low-memory signal that did not actually mean memory pressure. Update to v2.1.203 or later to restore instant switching. The actual possibly low memory — free some up and retry failure on memory-starved hosts is a separate path and is described above.

Option B: Minimum fix

Add only the v2.1.203 row to the version history table so users searching for the symptom have a pointer. Leave the troubleshooting section alone; the table entry alone is enough for a user who already knows what they are looking at.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/agent-view | Version history table (no v2.1.203 row) and Troubleshooting section (no macOS stall entry) |

Total scope: 1 page affected.

The release notes for v2.1.203 introduce this fix alongside several other macOS regression fixes (background agent audit-session failure, daemon session-token staleness, attached-session subagent drop, PATH inheritance from the dispatching shell, ANTHROPIC_BASE_URL drop, etc.). Only the false low-memory stall is in scope for this issue; the other regressions are separate documentation gaps if they are not yet reflected in the agent-view version history table or troubleshooting section.