{"version":"2.1.314","anchor":"remote-memory-path-warmup-before-tool-validation","canonical_anchor":"remote-memory-path-warmup-before-tool-validation","heading":"Paths in remote memory folders are looked up before a tool checks them","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/remote-memory-path-warmup-before-tool-validation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Paths in remote memory folders are looked up before a tool checks them\n\nWhen a tool is given a path inside a remote memory folder, Claude Code now looks that path up before checking the tool's input\n\n**What**\n\nA tool is one of the actions Claude Code can take, such as reading or editing a file. Some sessions have remote memory mounts: storage held elsewhere that appears to Claude Code as an ordinary folder.\n\nWhen a tool is given a path inside one of these folders, Claude Code now makes a quick first lookup of that path before it checks whether the tool's input is valid. This first lookup is called a warmup.\n\n**Why**\n\nA remote folder can be slow to respond, or fail, the first time it is touched. Looking the path up early is meant to cut that first-access delay and the failures that come with it.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}