{"version":"2.1.248","anchor":"restricted-counts-as-a-non-default-sdk-setting","canonical_anchor":"restricted-counts-as-a-non-default-sdk-setting","heading":"restricted counts as a non-default SDK setting","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/restricted-counts-as-a-non-default-sdk-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### `restricted` counts as a non-default SDK setting\n\nStarting a session with restricted now counts as a non-default configuration.\n\n**What**\n\nA session started with the `restricted` option is now treated as non-default, the same way skipping permission prompts or allowing bypass already were.\n\n**Evidence**\n\n`Boolean(n.restricted) ||`\n\n- Area: SDK\n- Names: `restricted`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}