{"version":"2.1.248","anchor":"new-sessions-started-from-fleet-view-inherit-restricted","canonical_anchor":"new-sessions-started-from-fleet-view-inherit-restricted","heading":"New sessions started from fleet view inherit --restricted","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/new-sessions-started-from-fleet-view-inherit-restricted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### New sessions started from fleet view inherit `--restricted`\n\nNew background sessions started from a restricted session inherit --restricted.\n\n**What**\n\nStarting a new background session from a session that was itself launched with `--restricted` now passes `--restricted` to the child. Previously the child started unrestricted.\n\n**Details**\n\n- Decided by the parent's own launch options; if the parent was not restricted, nothing changes.\n\n**Evidence**\n\n`restrictedSession()`\n\n- Area: Permissions\n- Names: `--restricted`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}