›_ Claude Code Issues
Claude Code Issues / #26168

[DOCS] No centralized reference for all Claude Code files and directories on disk

Status Fixed / completed
Maintainer reply None cached
Activity 7 comments · opened Feb 16, 2026 · closed Jun 27, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

There is no page or section that provides a consolidated view of all files and directories Claude Code uses on disk. The information is spread across at least 6 separate documentation pages.

Current Documentation

File and directory locations are documented piecemeal across multiple pages:

  • Settings page documents: ~/.claude/settings.json, .claude/settings.json, .claude/settings.local.json, ~/.claude.json, managed settings paths
  • Memory page documents: ~/.claude/CLAUDE.md, CLAUDE.md, .claude/CLAUDE.md, CLAUDE.local.md, ~/.claude/projects/<project>/memory/, .claude/rules/, ~/.claude/rules/
  • VS Code page documents: ~/.vscode/globalStorage/anthropic.claude-code/ (only in uninstall section)
  • Permissions page documents: managed settings file paths per OS
  • Keybindings page documents: ~/.claude/keybindings.json
  • MCP page documents: .mcp.json, managed MCP paths
  • Chrome page documents: native messaging host paths

No single page lists all of these together.

What's Wrong or Missing?

Users performing any of these common tasks have no single reference:

  1. Migrating to a new machine — need to know every file to copy
  2. Auditing what Claude Code stores — security review or privacy assessment
  3. Backing up configuration — need to know which files to include
  4. Troubleshooting — need to know where to look for state/cache/config issues
  5. Enterprise deployment — IT needs to understand the full disk footprint

Currently, users must read 6+ separate documentation pages and mentally compile the list. This is error-prone — it's easy to miss a file.

Suggested Improvement

Add a "Files and directories" section to the Settings page (or create a dedicated reference page) that lists every file/directory in one place:

Suggested addition:

### Files and directories Claude Code stores data in these locations: | Path | Purpose | Managed by | |------|---------|------------| | ~/.claude/settings.json | User settings | You (edit directly) | | ~/.claude/keybindings.json | Keyboard shortcuts | You (edit directly) | | ~/.claude/CLAUDE.md | Personal instructions | You (edit directly) | | ~/.claude/rules/*.md | Personal rules | You (edit directly) | | ~/.claude/agents/ | User subagents | You (edit directly) | | ~/.claude/plans/ | Plan files | Claude Code | | ~/.claude/projects/ | Per-project auto memory | Claude Code | | ~/.claude.json | Preferences, OAuth, MCP servers, caches | Claude Code | | ~/.vscode/globalStorage/anthropic.claude-code/ | Extension data, conversations | Claude Code | | .claude/settings.json | Project settings (shared) | You (edit directly) | | .claude/settings.local.json | Project settings (personal) | You (edit directly) | | .claude/CLAUDE.md | Project instructions | You (edit directly) | | .claude/rules/*.md | Project rules | You (edit directly) | | .claude/agents/ | Project subagents | You (edit directly) | | .mcp.json | Project MCP servers | You (edit directly) | | CLAUDE.md | Project instructions (root) | You (edit directly) | | CLAUDE.local.md | Personal project preferences | You (edit directly) |

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:
| Page | What it documents (partially) |
|------|-------------------------------|
| https://code.claude.com/docs/en/settings | settings.json files, ~/.claude.json |
| https://code.claude.com/docs/en/memory | CLAUDE.md files, auto memory, rules/ |
| https://code.claude.com/docs/en/vs-code | Extension storage (uninstall only) |
| https://code.claude.com/docs/en/permissions | Managed settings paths |
| https://code.claude.com/docs/en/keybindings | Keybindings file |
| https://code.claude.com/docs/en/mcp | MCP config files |

Total scope: 6 pages with scattered file location information; no single reference exists.

A centralized reference would also help the docs team maintain consistency — when a new file/directory is added, there would be an obvious place to document it.

View original on GitHub ↗

6 Comments

coygeek · 6 months ago

Follow-Up Verification (2026-02-21)

I re-verified this issue against the current documentation mirror.

Results

| Claim | Status |
|-------|--------|
| File/directory info scattered across 6+ pages | ❌ UNRESOLVED |
| No single page lists all files/directories | ⚠️ PARTIALLY RESOLVED (two partial tables now exist) |
| Common tasks (migration, audit, backup) lack a single reference | ❌ UNRESOLVED |

What's Improved

The documentation now contains two partial centralized references that didn't exist before:

  1. Settings page (settings.md, lines 66–72) — "What uses scopes" table covering Settings, Subagents, MCP servers, Plugins, and CLAUDE.md across User/Project/Local scopes
  2. Troubleshooting page (troubleshooting.md, lines 191–213) — "Configuration file locations" table covering settings, state, and MCP files

What's Still Missing

Neither table is comprehensive. Both are missing these paths that are documented on other pages:

| Missing path | Documented on |
|---|---|
| ~/.claude/keybindings.json | Keybindings page |
| ~/.claude/rules/*.md | Memory page |
| .claude/rules/*.md | Memory page |
| ~/.claude/projects/<project>/memory/ | Memory page |
| ~/.claude/plans/ | Settings page (buried in settings table) |
| ~/.vscode/globalStorage/anthropic.claude-code/ | VS Code page (uninstall section only) |
| Native messaging host paths (Chrome/Edge) | Chrome page |
| Managed CLAUDE.md paths (OS-specific) | Memory page |
| CLAUDE.local.md | Memory page |

File/directory information remains spread across at least 8 distinct pages: settings, troubleshooting, memory, keybindings, MCP, permissions, VS Code, Chrome, and sub-agents.

Impact

The five use cases from the original issue remain impacted — a user performing machine migration, security audit, backup, troubleshooting, or enterprise deployment would still need to consult 6+ separate pages to get a complete picture of Claude Code's disk footprint.

Recommendation

KEEP OPEN — The core request for a single consolidated reference of all files and directories remains unaddressed, though the two partial tables are an improvement.

coygeek · 5 months ago

Still unresolved as of 2026-03-17. No centralized files/directories reference exists. Information is scattered across settings.md and setup.md uninstall section.

coygeek · 5 months ago

Correction after a full re-verification on 2026-04-01: this issue is still only partially resolved, not resolved. The new claude-directory page is a meaningful central reference, but it still does not provide a complete single-page inventory of all documented on-disk locations such as the plans directory, managed MCP paths, VS Code extension storage, and browser native messaging host files, so this should remain open.

coygeek · 3 months ago

Still relevant as of 2026-05-18. This documentation gap has not been addressed in the docs yet.

coygeek · 2 months ago

Verified against the latest docs; this still appears unresolved.

coygeek · 2 months ago

Issue #26168 Verification

Title: [DOCS] No centralized reference for all Claude Code files and directories on disk
Issue Date: 2026-02-16
Verification Date: 2026-06-27
Status: RESOLVED

---

Issue Summary

The issue reports that there is no single documentation page that consolidates all of the files and directories Claude Code writes to or reads from on disk. File location information was reportedly scattered across at least six pages (settings, memory, VS Code, permissions, keybindings, MCP, Chrome), and the reporter requested a centralized reference to make migration, auditing, backup, troubleshooting, and enterprise deployment tasks easier.

---

Verification Results

Claim 1: There is no centralized reference page listing all Claude Code files and directories on disk.

Status: RESOLVED

A dedicated page titled "Explore the .claude directory" now exists and serves as the centralized reference the issue requested. The page opens with an explicit one-line summary of every file and directory it covers:

At https://code.claude.com/docs/en/claude-directory (line 7 of the mirror):

Where Claude Code reads CLAUDE.md, settings.json, hooks, skills, commands, subagents, workflows, rules, and auto memory. Explore the .claude directory in your project and ~/.claude in your home directory.

The page renders an interactive tree of every Claude Code filesystem location, with docsLink, description, and per-node metadata for each entry. The mirror contains 73 references to such documentation links/entries on the page, and the manifest records the page at docs/en/claude-directory.md with last_updated: 2026-06-11T19:00:16Z — meaning the page is current and actively maintained.

Verdict: The dedicated page at https://code.claude.com/docs/en/claude-directory is the centralized reference the issue asked for.

---

Claim 2: Information is spread piecemeal across at least six separate pages.

Status: RESOLVED

The new claude-directory page consolidates every file and directory the issue enumerated. Each of the seven categories from the "Current Documentation" section of the issue body now has a labeled node in the page's tree, with per-node documentation:

| File/directory the issue mentioned | Now consolidated on the centralized page |
|-----------------------------------|------------------------------------------|
| ~/.claude/settings.json | https://code.claude.com/docs/en/claude-directory — node global-settings (lines 472–490 of the mirror) |
| .claude/settings.json | Same page — node settings-json (lines 107–139) |
| .claude/settings.local.json | Same page — node settings-local-json (lines 141–160) |
| ~/.claude.json | Same page — node claude-json (lines 424–444) |
| ~/.claude/CLAUDE.md | Same page — node global-claude-md (lines 455–470) |
| CLAUDE.md and .claude/CLAUDE.md | Same page — node claude-md (lines 28–54) |
| ~/.claude/projects/<project>/memory/ | Same page — node global-projects and memory-dir (lines 536–600) |
| .claude/rules/, ~/.claude/rules/ | Same page — nodes rules (lines 161–212) and global-rules (lines 602–611) |
| ~/.claude/keybindings.json | Same page — node keybindings (lines 491–514) |
| .mcp.json | Same page — node mcp-json (lines 56–78) |
| ~/.claude/agents/, .claude/agents/ | Same page — nodes agents (lines 330–363) and global-agents (lines 668–677) |
| ~/.claude/skills/, .claude/skills/ | Same page — nodes skills (lines 214–282) and global-skills (lines 613–621) |
| ~/.claude/commands/, .claude/commands/ | Same page — nodes commands (lines 284–317) and global-commands (lines 624–634) |
| ~/.claude/output-styles/, .claude/output-styles/ | Same page — nodes output-styles (lines 319–328) and global-output-styles (lines 636–666) |
| ~/.claude/themes/ | Same page — node themes (lines 516–534) |
| .claude/workflows/, ~/.claude/workflows/ | Same page — nodes workflows (lines 365–374) and global-workflows (lines 679–688) |
| .worktreeinclude | Same page — node worktreeinclude (lines 80–97) |
| .claude/agent-memory/, ~/.claude/agent-memory/ | Same page — nodes agent-memory (lines 376–417) and global-agent-memory (lines 690–700) |

Verdict: Every filesystem location the issue body enumerated is now documented under a single canonical URL. The information is no longer scattered across six pages with no consolidated view.

---

Claim 3: The new reference is discoverable from related pages.

Status: RESOLVED

claude-directory is linked from at least seven other documentation pages, so users who start from any of the originally-cited pages can find it:

Verdict: The reference is reachable from the troubleshooting, devcontainer, data-usage, CLI, and glossary surfaces — covering the migration, auditing, and troubleshooting use cases the issue cited.

---

Current State

| Claim | Status |
|-------|--------|
| 1. No centralized reference page exists | RESOLVED |
| 2. Information spread across six pages | RESOLVED |
| 3. Reference is discoverable from related pages | RESOLVED |

---

Suggested Fix

N/A — issue has been resolved. A dedicated claude-directory page now provides the centralized reference the reporter asked for, and downstream pages link into it.

---

References

  • URL: https://code.claude.com/docs/en/claude-directory
  • Lines 5–7: Page title "Explore the .claude directory" and one-line summary listing every file/directory covered (CLAUDE.md, settings.json, hooks, skills, commands, subagents, workflows, rules, auto memory)
  • Lines 28–54: Project CLAUDE.md
  • Lines 56–78: Project .mcp.json
  • Lines 80–97: .worktreeinclude
  • Lines 107–139: Project settings.json
  • Lines 141–160: Project settings.local.json
  • Lines 161–212: Project rules/
  • Lines 214–282: Project skills/
  • Lines 284–317: Project commands/
  • Lines 319–328: Project output-styles/
  • Lines 330–363: Project agents/
  • Lines 365–374: Project workflows/
  • Lines 376–417: Project agent-memory/
  • Lines 424–444: ~/.claude.json
  • Lines 455–470: User ~/.claude/CLAUDE.md
  • Lines 472–490: User ~/.claude/settings.json
  • Lines 491–514: User ~/.claude/keybindings.json
  • Lines 516–534: User ~/.claude/themes/
  • Lines 536–600: User ~/.claude/projects/ and MEMORY.md
  • Lines 602–611: User ~/.claude/rules/
  • Lines 613–621: User ~/.claude/skills/
  • Lines 624–634: User ~/.claude/commands/
  • Lines 636–666: User ~/.claude/output-styles/
  • Lines 668–677: User ~/.claude/agents/
  • Lines 679–688: User ~/.claude/workflows/
  • Lines 690–700: User ~/.claude/agent-memory/
  • Manifest last_updated: 2026-06-11T19:00:16Z
  • URL: https://code.claude.com/docs/en/debug-your-config
  • Line 115: .claude directory reference: every config file location and what reads it
  • URL: https://code.claude.com/docs/en/how-claude-code-works
  • Line 97: application data in ~/.claude
  • URL: https://code.claude.com/docs/en/devcontainer
  • Lines 15, 88, 187: claude-directory linked from volume mount, credentials, and "See also" sections
  • URL: https://code.claude.com/docs/en/data-usage
  • Line 54: application data for what's stored and how to clear it
  • URL: https://code.claude.com/docs/en/cli-reference
  • Line 37: Clear local data for claude project purge
  • URL: https://code.claude.com/docs/en/glossary
  • Lines 87 and 217: The .claude directory glossary entries

---

Conclusion & Recommendation

Primary Concern: There was no single reference page listing every Claude Code file and directory on disk; users had to compile the list from six+ pages.

Resolution Status: RESOLVED

Recommendation: CLOSE

A dedicated centralized reference at https://code.claude.com/docs/en/claude-directory now lists every file and directory the issue enumerated, documents the purpose and scope of each, and is linked from the troubleshooting, devcontainer, data-usage, CLI, and glossary surfaces that the reporter identified as common starting points.

Showing cached comments. Read the full discussion on GitHub ↗

Related Claude Code issues

Matched on shared title terms, labels, topic and reported release — ranked so issues with real discussion come first.

Browse by topic

Same class of failure, ranked by community engagement — this issue is one of many, so it may not appear in the visible list: MCP server connection issues, IDE & terminal integration

Browse all Claude Code issue topics →