[DOCS] `claude agents` returning to the list does not document that in-flight background subagents now carry over

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

The "Attach to a session" subsection (around the description of pressing ← to detach and return to agent view), the "From inside a session" subsection under "Dispatch new agents", and the "Version history" table at the bottom of agent-view.md.

Current Documentation

The "Attach to a session" subsection describes returning to agent view as:

Press ← on an empty prompt, or run /exit, to detach and return to agent view. As of v2.1.198 this works the same way whether you opened the session from agent view or with claude attach <id> from your shell.

Detaching never stops a background session: ←, Ctrl+Z, /exit, and double Ctrl+C or double Ctrl+D all leave it running. To end a session from inside it, run /stop.

The "From inside a session" subsection describes the related /background flow as:

Backgrounding from an interactive session starts a fresh process that resumes from the saved conversation, and in-flight work moves to it: running background shell commands, backgrounded subagents, dynamic workflows, and scheduled tasks you created with /loop carry over to the background session and keep running there. A subagent moves together with everything it started, so it carries over only when all of that work can move too, including on Windows. To stop in-flight work instead of carrying it over, set the CLAUDE_DISABLE_ADOPT=1 environment variable; Claude Code then asks you to confirm before backgrounding.

The "Version history" table at the bottom of agent-view.md lists v2.1.198 as the most recent entry that addresses in-flight work on the ← and /background paths, and it does not include any v2.1.203 row:

| v2.1.198 | {/ min-version: 2.1.198 /}Agent view sends a notification through preferredNotifChannel when a background session needs input, finishes, or fails, and fires the Notification hook with the agent_needs_input or agent_completed type. ← and /exit inside claude attach <id> return to agent view instead of exiting to the shell; Ctrl+Z returns to the shell. A background session that isolated its work in a worktree commits, pushes its own isolated branch, never main or master, and opens a draft pull request when it finishes instead of asking first. /login runs in agent view and opens the sign-in dialog. The Background work is running exit dialog offers Move to background and exit. The exit handoff also covers background subagents, which resume from their transcript on the next wake instead of being reported as failed. claude --bg combined with -p or --print is rejected with an error. |

What's Wrong or Missing?

A. The "Detaching never stops a background session" claim is incomplete for subagents

The detach paragraph at line 191 says "Detaching never stops a background session" and lists ←, Ctrl+Z, /exit, and double Ctrl+C/Ctrl+D as keys that leave it running. Before v2.1.203, that statement was not actually true for subagents inside an attached session: returning to claude agents silently stopped running background subagents and re-ran the session's prompt from scratch instead of preserving the in-flight work. The current prose still does not acknowledge that v2.1.203 changed this behavior, so a user who relied on the documented "detach never stops the session" wording will not learn from the docs that subagent work now carries over on the return-to-claude agents path.

B. The "From inside a session" carry-over description is not tied to the detach path

The carry-over prose at line 305 is positioned under the /background heading and describes what happens when the user explicitly backgrounds a session with /background or /bg. It does not address the simpler, more frequent action of pressing ← (or /exit) inside claude attach <id> to go back to the agent-view list, which is the flow the v2.1.203 changelog entry is actually fixing. A user returning to claude agents after attaching to a session has no documented reason to believe the same carry-over rule applies.

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

The version history table at the bottom of agent-view.md documents v2.1.198, v2.1.199, v2.1.200, and v2.1.202, but stops at v2.1.202. Other v2.1.202 fixes in this same release cycle are surfaced with {/* min-version: 2.1.202 */} notes on other pages (e.g. commands.md, interactive-mode.md, permission-modes.md), but the v2.1.203 carry-over change for the detach path is missing from the table entirely. A user reading the version history table will not find the entry that explains why detaching now preserves subagent work.

Suggested Improvement

Add a short note to the "Attach to a session" subsection that explicitly extends the existing "Detaching never stops a background session" wording to background subagents. For example, immediately after the existing sentence:

Detaching never stops a background session: ←, Ctrl+Z, /exit, and double Ctrl+C or double Ctrl+D all leave it running. To end a session from inside it, run /stop.

extend it with:

Background subagents that are running in the attached session keep running after detach as well. Returning to claude agents no longer silently stops them or re-runs the session's prompt from scratch; the in-flight work carries over into the background session. Requires Claude Code v2.1.203 or later.

Cross-link the new sentence to the existing "From inside a session" carry-over description so users can read about both the /background and the ← paths in one place.

Also add a v2.1.203 row to the version history table at the bottom of agent-view.md:

| v2.1.203 | {/ min-version: 2.1.203 /}Returning to claude agents from an attached session no longer silently stops in-flight background subagents or re-runs the session's prompt from scratch; the subagent work carries over to the background session the same way it does when you use /background. |

If a v2.1.203 row already exists when this issue is reviewed, replace the prose-only note above with a cross-reference to that row rather than duplicating the version marker.

Impact

Medium - Makes feature difficult to understand

Additional Context

Changelog context (v2.1.203):

Fixed returning to claude agents silently stopping running subagents and re-running the prompt from scratch — their work now carries over

The user-facing symptom was that pressing ← (or /exit) inside an attached session appeared to keep the background session alive while actually terminating the running subagents and replaying the original prompt. After v2.1.203 the subagents continue running across the return, matching the behavior already documented for the /background flow.

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/agent-view | 185-193 | The "Attach to a session" subsection describes ← detach but does not mention subagent carry-over |
| https://code.claude.com/docs/en/agent-view | 299-309 | The "From inside a session" subsection documents carry-over for /background only |
| https://code.claude.com/docs/en/agent-view | 650-670 | The version history table ends at v2.1.202 and has no v2.1.203 row |

Total scope: 1 page affected, with three sections to update.