{"version":"2.1.321","anchor":"background-job-folder-creation-uses-mustexist-after-first-ma","canonical_anchor":"background-job-folder-creation-uses-mustexist-after-first-ma","heading":"Background jobs no longer recreate their folder after it has been made once","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/background-job-folder-creation-uses-mustexist-after-first-ma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Background jobs no longer recreate their folder after it has been made once\n\nOnce a background job's folder exists, or after a relaunch following a stall, Claude Code now expects the folder to exist instead of creating it again\n\n**What**\n\nA background job is a task Claude Code keeps running on its own. Each job has a folder. Claude Code used to create that folder every time it launched the job. Now, once the folder has been made, or after the job has been relaunched because attaching to it stalled, Claude Code requires the folder to already exist instead of creating it.\n\n**Why**\n\nA job folder that was removed is no longer quietly recreated when the job is relaunched.\n\n- Flag `tengu_bg_settled_crash_restart`: Not enough to say (read for one account on one subscription tier against v2.1.321; 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: Background Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}