{"version":"2.1.290","anchor":"background-job-respawn-can-fork-a-resume","canonical_anchor":"background-job-respawn-can-fork-a-resume","heading":"Restarting a background session can now continue as a copy","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/background-job-respawn-can-fork-a-resume","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Restarting a background session can now continue as a copy\n\nA restarted background session can now resume as a fresh copy with `--fork-session`, and a saved reply starting with \/ or ! gets a warning\n\n**Unclear.** What decides whether a restart continues the original session or a copy is not clear.\n\n**What**\n\nA background session is a Claude Code conversation that keeps running without a terminal window. When Claude Code restarts one, it can now use `--resume <id> --fork-session`, which continues the conversation under a new session ID instead of reusing the original. Before, a restart always resumed the same session.\n\nOther changes to restarts:\n\n- When a session is retried after Claude declined a request, the job's output and details are cleared and its saved list of links is reset.\n\n- If a saved reply begins with \/ or !, Claude Code warns that \"the saved reply starts with \/ or !, so no restart sends it\".\n\n**Why**\n\nRetrying a background session after a refusal now has its own path, which can start from a copy of the conversation.\n\n- Area: Sessions\n- Names: `--resume`, `--fork-session`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}