[Feature Request] Support external project-specific configuration storage in ~/.claude/project-specific/

Resolved 💬 5 comments Opened Apr 28, 2026 by kbcmdba Closed May 30, 2026

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.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗