{"version":"2.1.265","anchor":"instructionsloaded-fallback-check-via-sbe","canonical_anchor":"instructionsloaded-fallback-check-via-sbe","heading":"InstructionsLoaded fallback check via sbe()","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/instructionsloaded-fallback-check-via-sbe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### InstructionsLoaded fallback check via sbe()\n\nClaude Code now checks a fallback source to detect if InstructionsLoaded hooks are configured\n\n**Unclear.** What `sbe` checks or where it sources its answer from is not stated in the finding.\n\n**What**\n\nThe `InstructionsLoaded` hook fires when a CLAUDE.md file or a rules file is loaded into context, at session start or later when files are lazily loaded. Claude Code's internal check for whether any `InstructionsLoaded` hooks are registered now falls back to consulting `sbe(\"InstructionsLoaded\")` instead of always assuming none are active when it can't find any.\n\n**Why**\n\nThis makes detection of configured `InstructionsLoaded` hooks more reliable, reducing the chance that a hook that's actually set up gets incorrectly treated as absent.\n\n- Area: Hooks\n- Names: `InstructionsLoaded`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}