{"version":"2.1.224","anchor":"consent-to-dangerous-remote-settings-is-remembered-per-organ","canonical_anchor":"consent-to-dangerous-remote-settings-is-remembered-per-organ","heading":"Consent to dangerous remote settings is remembered per organization","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/consent-to-dangerous-remote-settings-is-remembered-per-organ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Consent to dangerous remote settings is remembered per organization\n\nApproving risky remote settings is now saved to a file so you aren't asked again.\n\n**What**\n\nWhen you approve remote settings that can run shell commands, set environment variables, install hooks or write CLAUDE.md, that approval is now written to a `remote-settings-consent.json` file so you are not asked again for the same content.\n\n**Details**\n\n- Records are keyed by organization uuid and store the account uuid, a hash of just the dangerous portion of the settings, and a timestamp. If that portion changes, the hash no longer matches and consent is requested again.\n- The file is written with 0600 permissions and the number of records is capped.\n- If the file is unreadable or was written by a newer version, it is left alone rather than overwritten.\n\n**Evidence**\n\n`Remote settings: Consent records file is `\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}