{"version":"2.1.283","anchor":"path-resolution-throws-when-there-is-no-working-directory","canonical_anchor":"path-resolution-throws-when-there-is-no-working-directory","heading":"Relative paths fail with an error when no working directory is known","tier":"notice","area":"File Reading","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/path-resolution-throws-when-there-is-no-working-directory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Relative paths fail with an error when no working directory is known\n\nWhen no base folder is available, a relative path now raises an error instead of being resolved against the process's current folder\n\n**Unclear.** It is not clear in which situations Claude Code has no base folder available.\n\n**What**\n\nA relative path is one given relative to some folder, such as `src\/app.js`. When Claude Code has no base folder to resolve such a path against, a relative or empty path now fails with an error. Before, it was resolved against the current folder of the Claude Code process. Absolute paths and paths starting with `~` still resolve as before.\n\n**Why**\n\nA relative path can no longer be quietly resolved against the wrong folder.\n\n- Area: File Reading\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}