Skip to content

docs: replace unsupported .claudeignore with permissions.deny rules #1877

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Yashasm18 wants to merge 1 commit into
base: v8
Choose a base branch
from
Open

docs: replace unsupported .claudeignore with permissions.deny rules #1877

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -597,12 +597,16 @@ graphify install # overwrites the skill file
```

**Claude Code prompt cache invalidated after every `graphify extract`**
Graphify writes output files (`graph.json`, `graphify-out/`) into the workspace. If those paths aren't ignored, every write invalidates Claude Code's prompt cache, forcing a full re-upload at cache-write rates on the next turn. Add them to `.claudeignore`:
```text
# .claudeignore
graph.json
graphify-out/
```
Graphify writes output files (`graph.json`, `graphify-out/`) into the workspace. If those paths aren't excluded, every write invalidates Claude Code's prompt cache, forcing a full re-upload at cache-write rates on the next turn. Claude Code does not read a `.claudeignore` file; use `permissions.deny` Read rules in `.claude/settings.json` instead:
```json
// .claude/settings.json
{
"permissions": {
"deny": ["Read(./graph.json)", "Read(./graphify-out/**)"]
}
}
```
Note that deny rules gate *access*, so this also stops the assistant from reading `graphify-out/` directly (e.g. browsing the generated wiki as navigation). If you rely on that workflow, keep the paths readable and accept the cache cost instead.

---

Expand Down