{"version":"2.1.267","anchor":"remote-settings-eligibility-now-excludes-hermetic-remote-ses","canonical_anchor":"new-session-type-hermetic-remote-sessions","heading":"New \"hermetic remote session\" restriction reason","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/remote-settings-eligibility-now-excludes-hermetic-remote-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New \"hermetic remote session\" restriction reason\n\nClaude Code now recognizes hermetic remote sessions as a distinct reason certain features are unavailable\n\n**What**\n\n- A new unavailability reason, \"hermetic remote session\", was added alongside existing reasons like `sandboxed_entrypoint` and `unpinned_gateway`.\n\n- The eligibility check for a background\/remote-settings feature now returns ineligible with reason `hermetic_remote_session` when running under `CLAUDE_CODE_REMOTE` combined with `CLAUDE_CODE_REMOTE_HERMETIC_MODE`, checked before the existing gateway\/first-party checks.\n\n**Why** This lets Claude Code report the correct, specific reason a feature is unavailable when running in a hermetic remote session, instead of falling through to a generic or misleading reason.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}