[DOCS] Agent view sleep/wake docs are outdated for background session recovery in v2.1.142

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

Background session lifecycle and sleep/wake behavior in the overview and troubleshooting sections

Current Documentation

The docs currently say:

Background sessions don't need any terminal open to keep working. A separate supervisor process runs them, so you can close agent view, close your shell, or start a new interactive session and your dispatched work keeps going. Session state persists on disk through auto-updates and supervisor restarts. If your machine sleeps or shuts down, running sessions stop; restart them with claude respawn --all.

And later:

Background sessions don't survive sleep or shutdown, so sessions that were running show as failed after you wake. Attach, peek, or reply to any of them and the session restarts from where it left off. To restart all of them at once, run claude respawn --all.

What's Wrong or Missing?

This appears outdated for v2.1.142.

The v2.1.142 changelog says:

Fixed background sessions disappearing and daemon reconnect failing after macOS sleep/wake — the daemon now detects clock jumps instead of treating them as elapsed idle time

The current agent-view page still tells readers that running background sessions stop on sleep and should be restarted with claude respawn --all. That no longer reflects the current behavior on macOS after the v2.1.142 fix, where the daemon can reconnect correctly across sleep/wake instead of treating the sleep interval as idle elapsed time.

As written, the page sets the expectation that sleep/wake always leaves sessions failed, which conflicts with the changelog fix and makes it unclear when respawn is actually needed.

Suggested Improvement

Update the sleep/wake guidance in agent-view to distinguish shutdown from macOS sleep/wake behavior in v2.1.142 and later.

For example:

Before:

Session state persists on disk through auto-updates and supervisor restarts. If your machine sleeps or shuts down, running sessions stop; restart them with claude respawn --all.

After:

Session state persists on disk through auto-updates and supervisor restarts. Shutdown still stops running sessions. On macOS, v2.1.142 and later also handle sleep/wake more reliably: the daemon reconnects background sessions after wake instead of treating the sleep interval as elapsed idle time. If a session does stop, restart it with claude respawn --all.

The troubleshooting section should make the same distinction so users know whether to wait for reconnect or manually respawn.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/agent-view | 120-122 | Overview says running sessions stop if the machine sleeps or shuts down |
| https://code.claude.com/docs/en/agent-view | 404-406 | Troubleshooting says background sessions stop after sleep and should be restarted |

Total scope: 1 page affected

Version context: v2.1.142 changelog entry says background sessions no longer disappear after macOS sleep/wake because the daemon now detects clock jumps instead of treating them as elapsed idle time.