Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Support hidden config files (e.g. .claude/CLAUDE.md or .CLAUDE.md) for project-level instruction [1 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#54183•Fetched 2026-04-29 06:34:03
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
lulukdoglulukdog
Participants
github-actions[bot]github-actions[bot]lulukdoglulukdog
Timeline (top)
labeled ×2commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

When using CLAUDE.md or CLAUDE.local.md for project-level instructions, the files are always visible in the project root directory. For users who want to keep their workspace clean and don't want these config files cluttering the file listing, there is no hidden file option. The only way to avoid visible files is using the global ~/.claude/CLAUDE.md, which cannot provide project-specific instructions.

Proposed Solution

Support hidden config file locations at the project level, for example:

  • .claude/CLAUDE.md (hidden directory, similar to .git/, .vscode/)
  • .CLAUDE.md (hidden file with dot prefix)

Claude Code would look for instructions in these locations in addition to the existing CLAUDE.md and CLAUDE.local.md. Priority order could be: CLAUDE.md > .CLAUDE.md > .claude/CLAUDE.md (or merged).

Alternative Solutions

Currently I work around this by using the global ~/.claude/CLAUDE.md for personal preferences, but this doesn't support project-specific instructions without a visible file. Adding CLAUDE.local.md to .gitignore avoids git tracking but the file is still visible in the directory listing and IDE file explorer.

Priority

High - Significant impact on productivity

Feature Category

File operations

Use Case Example

  1. I have a monorepo workspace directory with multiple projects
  2. I want project-specific Claude Code instructions without adding visible files to the root
  3. With this feature, I could place instructions in .claude/CLAUDE.md — the dotfile convention keeps the workspace root clean, consistent with how .git/, .vscode/, .idea/ work
  4. This is especially useful when the project root already has many config files and I want to reduce clutter

Additional Context

The dotfile/dot-directory convention is well-established in the ecosystem (.git, .vscode, .eslintrc, .prettierrc, etc.). Supporting .claude/ as a hidden config directory would feel natural to most developers and align with existing tooling patterns.

extent analysis

TL;DR

Supporting hidden config file locations, such as .claude/CLAUDE.md or .CLAUDE.md, would allow users to keep their workspace clean while still providing project-specific instructions.

Guidance

  • Consider adding support for hidden config file locations, such as .claude/CLAUDE.md or .CLAUDE.md, to the existing config file search order.
  • Evaluate the proposed priority order: CLAUDE.md > .CLAUDE.md > .claude/CLAUDE.md to ensure it meets the requirements.
  • Review the use case example to understand the benefits of supporting hidden config files in a monorepo workspace directory.
  • Investigate how other tools and ecosystems use the dotfile/dot-directory convention to ensure consistency and alignment with existing patterns.

Notes

The proposed solution aligns with established conventions in the ecosystem, and supporting hidden config files would provide a natural and intuitive way for developers to manage their workspace.

Recommendation

Apply workaround: Support hidden config file locations, such as .claude/CLAUDE.md or .CLAUDE.md, to provide project-specific instructions without cluttering the workspace. This would improve productivity and align with existing tooling patterns.

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…
#output truncation#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING