{"version":"2.1.299","anchor":"hooks-modules-read-switch-changes-how-the-background-launch","canonical_anchor":"hooks-modules-read-switch-changes-how-the-background-launch","heading":"Background launches now depend on hook modules being switched on","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/hooks-modules-read-switch-changes-how-the-background-launch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Background launches now depend on hook modules being switched on\n\nWhether a background launch rule applies now also depends on the hook modules runtime being switched on\n\n**Unclear.** What switches the hook modules runtime on, and so when background launches now apply, is not clear.\n\n**What**\n\nClaude Code has a check that decides whether a background launch rule applies. Before, the check passed whenever such a rule was set. Now it also needs the runtime that loads hook modules to be switched on, plus two further conditions. Hooks are your own scripts that Claude Code runs at certain moments.\n\n**Why**\n\nThis ties background launches to whether hook modules are running, so a background launch rule that worked before may not take effect if that runtime is off.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}