[DOCS] Background-agent update docs still describe stale workers surviving until attach

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

"The supervisor process," specifically the paragraphs covering binary updates, worker restarts, and attach behavior.

Current Documentation

The agent-view guide currently says:

"The supervisor watches the installed Claude Code binary on disk and restarts into the new version after the regular auto-updater replaces it. Background sessions are detached processes, so they keep running through the restart and the new supervisor reconnects to them. An idle pinned session is also restarted in place onto the new version so it picks up the update without you reattaching."

The wording singles out idle pinned sessions for an immediate worker restart and otherwise says detached background sessions keep running through the supervisor update.

What's Wrong or Missing?

Claude Code v2.1.206 changes the update lifecycle: background agents upgrade to the new version in the background immediately after a Claude Code update. Users no longer need to pay the stale-session upgrade delay when they later attach.

The current prose can be read to mean that non-pinned background workers remain on their old process after the supervisor reconnects and only upgrade on a later wake or attach. It does not describe the proactive post-update worker upgrade, which sessions qualify, what status appears during it, or what happens to active work.

Suggested Improvement

Update the binary-watch paragraph to state that v2.1.206 proactively upgrades background-agent workers after an installed Claude Code update. Explain:

1. Whether working, waiting, idle, stopped, and pinned sessions all follow the same upgrade timing.
2. That active background work is handed off across the process restart under the existing handoff rules.
3. What status is shown in agent view while a worker upgrades.
4. That attaching after the upgrade should no longer incur a stale-session restart delay.

Retain the existing claude attach retry guidance for the case where a user attaches while an upgrade is still in progress.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/agent-view | 559-566 | Supervisor update, worker restart, and attach behavior |

Total scope: 1 page affected.

Version: Proactive background-agent upgrade behavior added in Claude Code v2.1.206.