docs(models): explain why Bash commands need absolute paths - #8
Merged
Merged
Conversation
Add a Bash commands section describing that relative paths after a cd cannot be resolved by the permission checker, so every such command triggers an approval prompt. Replace the older token-rule bullet with a pointer to the new section. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
gsdevme
marked this pull request as ready for review
September 7, 2026 09:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
## Bash commandssection tomodels.mdrecommending absolute paths built from the repository root instead ofcd <dir> && <cmd>with relative paths.cd, so every such command prompts for approval.Test plan
make testpassesmake applyand confirm the section appears in~/.claude/CLAUDE.mdimports and the generated CodexAGENTS.md🤖 Generated with Claude Code