{"version":"2.1.285","anchor":"isolation-latch-reworked-for-session-based-web-exemption","canonical_anchor":"isolation-latch-reworked-for-session-based-web-exemption","heading":"Some tools no longer lock a session into one isolation mode","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/isolation-latch-reworked-for-session-based-web-exemption","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Some tools no longer lock a session into one isolation mode\n\nTools that Claude Code now treats as web tools no longer lock the session into a single isolation mode, and that check now depends on the session\n\n**Unclear.** It is not clear which tools fall into the category that is now treated as web tools.\n\n**What**\n\nWhen certain tools run, Claude Code can lock the session into one isolation mode for the rest of the conversation. A tool is an action Claude Code takes, such as running a command. Isolation is how separated that work is kept from the rest of your system.\n\nBefore this build, a tool's category was used directly to decide whether to set that lock. The check now also depends on the current session. Tools that fall into one particular category are treated as web tools, and they no longer set the lock.\n\n**Why**\n\nRunning some tools may no longer tie the rest of the session to a single isolation mode.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}