{"version":"2.1.300","anchor":"seededremote-file-stat-paths-short-circuit-when-file-is-not","canonical_anchor":"seededremote-file-stat-paths-short-circuit-when-file-is-not","heading":"File time checks stop early when the file is not on this machine","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/seededremote-file-stat-paths-short-circuit-when-file-is-not","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### File time checks stop early when the file is not on this machine\n\nClaude Code no longer looks a file up on disk for its timestamps when the file is not on this machine\n\n**What**\n\nWhen Claude Code is in a setting where a file is not stored on this machine, such as a remote session, two of its checks for a file's details no longer look the file up. Depending on the check, Claude Code either reports the current time or stops with an error such as \"seeded file not on this machine\".\n\n**Why**\n\nThis affects the modification times Claude Code reports for files in remote or served sessions.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}