{"version":"2.1.312","anchor":"remote-session-tool-lookup-gains-a-second-table-used-only-w","canonical_anchor":"remote-session-tool-lookup-gains-a-second-table-used-only-w","heading":"Remote sessions launched without disk access can look up an extra set of tools","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/remote-session-tool-lookup-gains-a-second-table-used-only-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote sessions launched without disk access can look up an extra set of tools\n\nWhen a remote session is launched without disk access, tool lookups can now fall back to a second set of handlers\n\n**What**\n\nIn remote sessions, Claude Code finds the handler for a tool by name in one table. It can now fall back to a second table when the session was launched in diskless mode, meaning without its own disk to work on.\n\n**Why**\n\nThis mainly matters to hosts that run Claude Code diskless. Ordinary use from the command line is likely unaffected.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}