{"version":"2.1.251","anchor":"permission-mode-corrected-when-feature-flags-arrive-late","canonical_anchor":"permission-mode-corrected-when-feature-flags-arrive-late","heading":"Permission mode corrected when feature flags arrive late","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/permission-mode-corrected-when-feature-flags-arrive-late","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Permission mode corrected when feature flags arrive late\n\nYour permission mode is re-checked once remote settings load, so startup no longer sticks on the wrong one.\n\n**What**\n\nAt startup the permission mode is sometimes decided before the remote feature-flag cache has loaded, which could settle on the wrong mode. Claude Code now re-resolves the mode once the cache is populated and re-applies it if the answer differs, logging a warning when it does.\n\n**Details**\n\n- The correction deliberately will not switch you into bypassPermissions when that mode is unavailable, nor into auto mode when the auto-mode gate is off.\n- Which mode is ultimately chosen still depends on remote feature-flag configuration.\n\n**Evidence**\n\n`startup resolved ${e.mode} against an empty GrowthBook cache; re-resolved to ${r.mode}`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}