[DOCS] Incorrect information on relative permission paths vs. settings.json or counter-intuitive behavior

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/permissions#read-and-edit

Section/Topic

Read and Edit using /path relative pattern

Current Documentation

The doc currently says /path Path relative to settings file Edit(/src/**/*.ts) <settings file path>/src/**/*.ts

What's Wrong or Missing?

Situation example: I launch Claude Code from /test. /test contains .claude/settings.json and /src. .claude/settings.json is
{
"permissions":
{
"deny": "Read(/src/**/*.ts)"
}
}

The behavior I would expect is that if I launch Claude Code in /test, the pattern is applied (/sec is in my working directory) and any .ts file cannot be edited.

Based on the documentation and chat with the bot on your I understand, that all .ts files in /test/src can be edited, only .ts files in /test/.claude/src (which does not even exist) can't be edited.

Therefore for me the behavior is counter intuitive (or the documentation is incorrect).

Suggested Improvement

If the documentation is correct - i would suggest to adjust how relative paths from settings.json are interpret within Claude Code and update the documentation accordingly.

If the documentation is not correct, fix it.

Impact

Medium - Makes feature difficult to understand

Additional Context

_No response_