{"version":"2.1.222","anchor":"isolation-refusal-messages-distinguish-session-from-agent","canonical_anchor":"isolation-refusal-messages-distinguish-session-from-agent","heading":"Isolation refusal messages distinguish session from agent","tier":"notice","area":"Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/isolation-refusal-messages-distinguish-session-from-agent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Isolation refusal messages distinguish session from agent\n\nIsolation refusal messages now say whether the session or the agent is the one confined.\n\n**What**\n\nThe refusals you get when a shell cwd or file edit escapes a worktree now name the right subject.\n\n**Details**\n\n- picks between \"This session is isolated\u2026\" and \"This agent is isolated\u2026\" based on whether the pin is the session's own worktree, with a matching possessive\n- shell cwd and file edit paths now share one escape-detection routine\n\n**Evidence**\n\n`possessive: \"a worktree-isolated agent's\"`\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}