{"version":"2.1.232","anchor":"fork-refusal-builds-its-flag-list-from-one-place","canonical_anchor":"fork-refusal-builds-its-flag-list-from-one-place","heading":"Fork refusal builds its flag list from one place","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/fork-refusal-builds-its-flag-list-from-one-place","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Fork refusal builds its flag list from one place\n\nThe can't-fork message builds its flag list from one shared constant; the text is unchanged.\n\n**What**\n\nThe \"Can't fork\" message no longer hardcodes the list of launch flags that block forking; it interpolates a shared constant, so the enumerated flags are defined once. The visible text about safe or bare mode is unchanged.\n\n**Evidence**\n\n`Can't fork: this session was started with launch flags (safe or bare mode, `\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}