{"version":"2.1.281","anchor":"internal-builds-refused-bypasspermissions-outside-a-sandbox","canonical_anchor":"internal-builds-refused-bypasspermissions-outside-a-sandbox","heading":"Internal builds refused bypassPermissions outside a sandbox when claiming a session","tier":"internal","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/internal-builds-refused-bypasspermissions-outside-a-sandbox","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Internal builds refused bypassPermissions outside a sandbox when claiming a session\n\nInternal builds can no longer take over a session that uses bypassPermissions outside a sandbox\n\n**Unclear.** The finding does not say which builds count as internal or when that check returns true.\n\n**What**\n\nClaiming a session means taking over a session that was started somewhere else. If one of the permission modes in play for that session is `bypassPermissions`, the claim now fails when `bypassPermissionsDeniedToInternalBuild()` returns true. `bypassPermissions` is the mode that skips permission prompts.\n\nThe error is `permission_mode_not_claimable`, with the message \"Bypass permissions mode is not available to internal builds outside a sandbox\". It tells you to start the session cold, meaning start it fresh instead of taking it over.\n\n**Why**\n\nIf you see this error, the way forward is to start a new session rather than hand the existing one over.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}