{"version":"2.1.287","anchor":"background-launch-rule-scaffolding-for-tools-and-a-stricter","canonical_anchor":"background-launch-rule-scaffolding-for-tools-and-a-stricter","heading":"Groundwork for custom background launch rules, and a stricter disable check","tier":"soon","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/background-launch-rule-scaffolding-for-tools-and-a-stricter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Groundwork for custom background launch rules, and a stricter disable check\n\nBackground tasks can now be disabled internally with a launch rule installed in their place, and `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS` still turns them off\n\n**Unclear.** Nothing shows what installs a background launch rule or when.\n\n**What**\n\nBackground tasks are commands or helpers that keep running while you carry on working. Claude Code gains a new internal setting that can disable background tasks and install a background launch rule in their place. A rule can only be installed once background tasks are disabled.\n\nBackground tasks now count as disabled when either:\n\n- they are disabled with no launch rule installed\n\n- `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS` is set\n\n**Why**\n\nThis looks like groundwork for letting something else take over how background tasks are launched. Setting `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS` continues to turn them off.\n\n- Area: Background Tasks\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}