{"version":"2.1.259","anchor":"background-forked-sessions-now-inherit-proactivitylevel","canonical_anchor":"background-forked-sessions-now-inherit-proactivitylevel","heading":"Background-forked sessions now inherit proactivityLevel","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/background-forked-sessions-now-inherit-proactivitylevel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Background-forked sessions now inherit proactivityLevel\n\nBackgrounding a session now carries the parent conversation's proactivity setting into the forked session.\n\nThe background-session-fork request builder now passes `proactivityLevel` into the fork call, wiring the parent conversation's proactivity setting through to a newly backgrounded session. This field was previously absent; the argument slot it now occupies held `alwaysDenyRules` in the prior build's order. The background-fork flow itself, triggered from the \"Background this session?\" confirmation dialog, is an existing feature, so this extends already-reachable functionality rather than adding a new gate.\n\n- Area: Sessions\n- Names: `proactivityLevel`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}