{"version":"2.1.216","anchor":"session-fork-more-specific-error-messages","canonical_anchor":"session-fork-more-specific-error-messages","heading":"Session Fork: More Specific Error Messages","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.216\/e\/session-fork-more-specific-error-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.216","markdown":"### Session Fork: More Specific Error Messages\n\n**What**\n\nWhen a session cannot be forked, the error now gives a specific reason rather than a generic refusal.\n\n**Details**\n\n- Persistence off: \"Can't fork: session persistence is off, so the new session would have nothing to start from.\"\n- Restricted flags: \"Can't fork: this session was started with launch flags (safe or bare mode, a custom system prompt, a tool allowlist, or restricted settings)...\"\n- Nothing to fork yet: \"Nothing to fork yet. Send a message first.\"\n- Messages have also been shortened and made direct (no more parenthetical asides about worktrees or agent view)\n\n**Evidence**\n\nFork error messages (search for `\"Can't fork: session persistence is off\"` or `\"Can't fork: this session was started with launch flags\"`)."}