{"version":"2.1.295","anchor":"background-job-attach-loop-can-stand-down","canonical_anchor":"background-job-attach-loop-can-stand-down","heading":"Reattaching to a background session can stop retrying, and exit waits briefly","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/background-job-attach-loop-can-stand-down","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Reattaching to a background session can stop retrying, and exit waits briefly\n\nWhen reconnecting to a background session, Claude Code can now stop retrying quietly, and on exit it waits up to 5 seconds for the session to settle\n\n**What**\n\nA background session is a Claude Code session that keeps running after you leave it, and you can attach to it again later. When the connection drops, Claude Code tries to reconnect in a loop. That loop now checks whether it should stand down, at the start of each try and when the background process fails to start. If so, it stops without the \"Couldn't restart\" error. It can also report that it detached before the first screen was drawn.\n\nWhen Claude Code shuts down, it now waits for the attached session to settle before exiting, for at most 5 seconds.\n\n**Why**\n\nReconnecting to a background session no longer always ends in endless \"Reconnecting\u2026\" messages or an error.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}