{"version":"2.1.285","anchor":"resuming-a-live-background-session-can-now-attach-to-it-and","canonical_anchor":"resume-picker-now-offers-to-open-a-live-background-session","heading":"Resuming a session that is running in the background now opens it and hands over your prompt","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/resuming-a-live-background-session-can-now-attach-to-it-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Resuming a session that is running in the background now opens it and hands over your prompt\n\nResuming a conversation that is still running in the background now attaches to it and delivers your prompt, instead of stopping with instructions\n\n**Unclear.** The full set of cases where the handoff applies instead of the refusal is not established.\n\n**What**\n\nA background session is a Claude Code conversation that keeps running without a terminal window attached to it. Before, choosing one in `\/resume` or with `claude --resume` stopped with a message saying the session was still running, and told you to run `claude attach` or `claude stop`. Now Claude Code tries to open it for you:\n\n- The session is opened as if you had run `claude attach <jobId>`, and Claude Code prints \"Opening ..., running in the background\".\n\n- If you gave a prompt, it is first sent to that session so it runs as the next turn.\n\n- Before handing over, Claude Code checks that the background session is running the same Claude Code build. If it is not, you get an `ESKEW` error.\n\n- This needs an interactive terminal for both input and output. It does not happen with conflicting flags such as an `--output-format` other than text.\n\n- The path sits behind `tengu_resume_open_live_bg`, whose built-in fallback is on when the server sends no value.\n\nIf opening fails or a launch prompt is still pending, a screen explains why. It now shows the session title followed by \" is running in the background\". It also says whether your prompt was queued, not confirmed, or not sent, and still suggests `claude attach`, `claude stop` and `claude --resume ... --fork-session`. A separate message tells you when your latest conversation is running in the background. It points to `claude agents` or `claude --resume`, and adds `--fork-session` when forking into a new copy is possible.\n\n**Why**\n\nResuming a busy background session no longer dead-ends, and a prompt you typed is not silently lost. You are told what happened to it.\n\n- Flag `tengu_resume_open_live_bg`: Not enough to say (read for one account on one subscription tier against v2.1.285; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Names: `--resume`, `claude attach`, `claude stop`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}