Plans should be stored in project folder, not global ~/.claude/plans/
Resolved 💬 2 comments Opened Feb 4, 2026 by koshak01 Closed Feb 4, 2026
Problem
Currently all plans are stored in a single global folder ~/.claude/plans/ regardless of which project they belong to.
When working with multiple projects, this creates confusion:
- Plans from different projects are mixed together
- No way to know which plan belongs to which project without reading content
- When switching between projects, old plans from other projects are still visible
Current behavior
~/.claude/plans/
├── plan-for-project-A.md
├── plan-for-project-B.md
└── plan-for-project-C.md # All mixed together
Expected behavior
Plans should be stored in the project's .claude/plans/ folder:
/path/to/project-A/.claude/plans/
└── some-plan.md
/path/to/project-B/.claude/plans/
└── another-plan.md
Benefits
- Clear separation between projects
- Plans are version-controlled with the project (if desired)
- Easy to clean up plans for specific project
- No confusion about which plan belongs where
- Consistent with how other project-specific files are stored in
.claude/
Workaround
Currently I have to manually check plan content to determine which project it belongs to.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗