{"version":"2.1.91","anchor":"relative-file-paths-in-tool-descriptions-gradual-rollout","canonical_anchor":"relative-file-paths-in-tool-descriptions-gradual-rollout","heading":"Relative File Paths in Tool Descriptions [Gradual Rollout]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.91\/e\/relative-file-paths-in-tool-descriptions-gradual-rollout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.91","markdown":"### Relative File Paths in Tool Descriptions [Gradual Rollout]\n\n**What**\n\nWhen enabled, tool descriptions instruct Claude to use relative (cwd-based) file paths instead of absolute paths, and the Bash tool description notes that `cd` does not persist between calls.\n\n**Status**\n\nFeature-flagged via `tengu_relpath_gh7k` (default: false)\n\n**Details**\n\n- Read tool description changes from \"must be an absolute path\" to \"can be relative to cwd (preferred for brevity) or absolute\"\n- Bash tool adds: \"Avoid `cd` unless the User explicitly requests it. The shell already starts in cwd\"\n- Read tool adds `ONLY include with offset to read a specific slice. OMIT to read the whole file`\n\n**Evidence**\n\nRelative path tool descriptions (gated by `tengu_relpath_gh7k`, search for `\"The file_path parameter can be relative to cwd\"`)"}