{"version":"2.1.292","anchor":"remote-file-read-supports-anchored-paths","canonical_anchor":"remote-file-read-supports-anchored-paths","heading":"Remote file reads can resolve paths against an anchor","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/remote-file-read-supports-anchored-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Remote file reads can resolve paths against an anchor\n\nRemote file reads accept an `anchor` (`workspace_root`, `diff_root` or a repo) so clients can read files without absolute paths\n\n**What**\n\nA remote client, such as the sidebar file viewer in a remote session, can ask Claude Code to read a file. Before, it had to give an absolute path, the full path from the top of the disk.\n\n- `anchor`: a new internal option on `read_file` (handled by `readFileForRemote`). It names a starting folder: `workspace_root` (the folder `list_directory` lists from), `diff_root`, or a repo given by owner and name. The path is resolved against that folder before reading.\n\n- Permission checks run on the resolved path.\n\n- The response includes an optional `anchor` field saying which kind of root was used.\n\n**Why**\n\nRemote viewers can open repository files by a path relative to the workspace or repo, and can tell which root a path was resolved against, while the usual permission checks still apply to the real file.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}