{"version":"2.1.314","anchor":"stage-file-store-check-via-filestore-metadata-gated-by-teng","canonical_anchor":"stage-file-store-check-via-filestore-metadata-gated-by-teng","heading":"Remote file staging can compare with the store and skip matching downloads","tier":"soon","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/stage-file-store-check-via-filestore-metadata-gated-by-teng","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Remote file staging can compare with the store and skip matching downloads\n\nRemote file staging gains a check that compares a local file's size and md5 with the filestore and, in mode on, skips the download if they match\n\n**Unclear.** Whether the comparison changes what Claude Code does or is only recorded, and how \"count\" differs from \"on\", is not shown.\n\n**What**\n\nIn remote sessions, Claude Code can stage a file, which means downloading a copy from a remote file store so it is available locally. New code can first ask the store for the file's details and compare them with the local copy:\n\n- Store lookup: it calls `\/v1\/filestore\/fs\/readFileMetadata` to get the file's size and md5 (a fingerprint of its contents) and compares them with the local file.\n\n- Local hashing: it computes the local file's fingerprint only when the local file is read-only (mode `0444`), has a single hard link and has the same size as the stored file.\n\n- Verdict: the result is one of `same_contents`, `md5_differs`, `size_differs`, `local_file_changed` and others.\n\n- Skipping: in mode `on`, a matching file is not downloaded again and the step is recorded as `already_present`. Before, the file was always fetched.\n\n- Pausing: if the check fails, it pauses for a set time or for the rest of the process (`stage_file_store_check_paused`).\n\n- Modes: the mode comes from the `tengu_quiet_ledger` gate, which accepts only `count`, `on` or `off` and falls back to `off` in the code. The staging step passes the gate value only when `e.force === !0`, and passes `off` otherwise. What `count` does differently from `on` was not traced.\n\n- Real path check: on Linux, the existing already-present check now confirms the file's real location through `\/proc\/self\/fd`.\n\nNothing has been read about the `tengu_quiet_ledger` or `tengu_stage_file_completed` gates, so whether this is active is not known.\n\n**Why**\n\nWhen the active mode is `on`, files that are already present and unchanged would not be downloaded again in remote sessions. The extra Linux path check makes the already-present decision rely on where the file really is.\n\n- Flag `tengu_quiet_ledger`: Not enough to say (read for one account on one subscription tier against v2.1.314; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}