claude-code - ๐Ÿ’ก(How to fix) Fix [Feature Request] Support external project-specific configuration storage in ~/.claude/project-specific/ [4 comments, 2 participants]

Official PRs (โ€ฆ)
ON THIS PAGE

Recommended Tools

ร—6

Utilities matched from this issueโ€™s tags and category โ€” try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful ยท Quick feedback

Loadingโ€ฆ
GitHub stats
anthropics/claude-code#54121โ€ขFetched 2026-04-28 06:38:41
View on GitHub
Comments
4
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
commented ร—4labeled ร—3
RAW_BUFFERClick to expand / collapse

Bug Description Claude is currently unable to store project-specific configuration information outside the project directory. This is both good and bad. For me, CLAUDE.md contains sensitive information that I don't want committed to GitHub, but I do want committed to ForgeJo (repository on my Proxmox cluster and NAS), so I have a backup (and log) of it. If Claude were able to optionally store project-specific CLAUDE.md information in ~/.claude/project-specific/projectId/CLAUDE.md and a separate ~/.claude/project-specific/project_list.md (with a list of IDs and associated project directories), Claude could check for that first before storing data in /path/to/project/CLAUDE.md. That would make it possible for me to store ~/.claude in Git under ForgeJo, but not in GitHub, keeping my data private.

Environment Info

  • Platform: linux
  • Terminal: tmux
  • Version: 2.1.119
  • Feedback ID: 2feace90-eda4-4b42-8007-ea524f1f82b8

Errors Truncated.


**Note:** Content was truncated.

extent analysis

TL;DR

Consider modifying Claude to store project-specific configuration information in a separate directory, such as ~/.claude/project-specific/, to keep sensitive data private.

Guidance

  • Investigate the current implementation of Claude's configuration storage to understand how it can be modified to support external storage.
  • Explore the possibility of adding a configuration option to specify an alternative storage location for project-specific data.
  • Determine the required changes to Claude's code to check for external configuration files before storing data in the project directory.
  • Consider the security implications of storing sensitive information in a separate location and ensure proper access controls are in place.

Notes

The provided issue lacks specific technical details about Claude's implementation, making it challenging to provide a comprehensive solution. The suggested approach assumes that Claude's code can be modified to support external configuration storage.

Recommendation

Apply workaround: Modify Claude to store project-specific configuration information in a separate directory, such as ~/.claude/project-specific/, to keep sensitive data private. This approach allows for flexible storage of sensitive information while maintaining the ability to commit non-sensitive data to version control.

Vote matrix ยท Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loadingโ€ฆ

Still need to ship something?

ร—6

Another batch ranked right after the header list โ€” different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - ๐Ÿ’ก(How to fix) Fix [Feature Request] Support external project-specific configuration storage in ~/.claude/project-specific/ [4 comments, 2 participants]