Manage sessions changedsessions
Nearest release: v2.1.304, published 6 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 20 Oct 2026 02:25 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+1added
Lines−5removed
From line
19
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits40to this page, all time
### Resume a running background session
The whole hunk
from line 19, old and new numbered
/
from line 19
1919| `claude --from-pr <number>` | Opens the session picker filtered to sessions linked to that pull request |
2020| `/resume` | Switches to a different session from inside an active session |
2121
22<h3 id="resume-a-running-background-session">
23 Resume a running background session
24</h3>
22### Resume a running background session
2523
2624When the conversation you resume with `claude --resume` or `/resume` belongs to a [background session](/docs/en/agent-view) that is still running, Claude Code opens the running session itself. With `--bg` on the command line, the resume is a [background dispatch](/docs/en/agent-view#from-your-shell) instead. Before v2.1.285, Claude Code refused and told you to open the session with `claude attach <id>`, or to stop it with `claude stop <id>` first.
2725
from line 76
7876| `plan` | Non-interactive, under the [conditions below](#resume-in-plan-mode-with-p) | Plan mode |
7977| Any mode | Non-interactive, in any other case | The permission mode a new `claude -p` run would start in |
8078| `plan` | VS Code | Plan mode, with [the exceptions on the VS Code page](/docs/en/vs-code#resume-past-conversations) |
81
82<a id="resume-in-plan-mode-with-p" />
8379
8480##### Resume in plan mode with `-p`
8581
No line in this hunk matches that.