{"version":"2.1.299","anchor":"memory-backend-lists-with-a-prefixes-field-stops-early-and","canonical_anchor":"memory-backend-lists-with-a-prefixes-field-stops-early-and","heading":"Reading a memory file by path takes fewer requests on repeat reads","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/memory-backend-lists-with-a-prefixes-field-stops-early-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Reading a memory file by path takes fewer requests on repeat reads\n\nClaude Code now remembers which memory file sits at which path and tries that first, instead of listing the folder on every read\n\n**What**\n\nClaude Code can keep memory files in a remote store. Before, reading one by its path always meant listing the folder it sits in, finding the file, and then reading it.\n\nNow Claude Code remembers the id of the file at each path and tries that id first. If that id no longer leads to that path, it falls back to listing the folder one level deep. Listings can also stop early once they reach a given path, and they can return folder prefixes as well as files.\n\n**Why**\n\nReading the same memory file again should take fewer requests and so return faster.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}