{"version":"2.1.296","anchor":"project-settings-approval-now-records-who-approved","canonical_anchor":"project-settings-approval-now-records-who-approved","heading":"Project settings approval now records how it was approved","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/project-settings-approval-now-records-who-approved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Project settings approval now records how it was approved\n\nClaude Code's check for approved project settings now notes whether approval came from settings, bypass or a non-interactive run\n\n**What**\n\nProject settings are settings stored with a project that need approval before Claude Code uses them. The check for this used to answer simply \"approved\" or \"pending\". It now also records how approval came about:\n\n- `settings`\n\n- `bypass`\n\n- `non_interactive`, meaning a run with nobody there to answer prompts\n\n**Why**\n\nThe approval result carries more information, but nothing looks different to you.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}