You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Claude consistently ignores being directed to store plan files in the repo #26226
I have searched existing issues and this hasn't been reported yet
This is a single bug report (please file separate reports for different bugs)
I am using the latest version of Claude Code
What's Wrong?
Despite having specified in CLAUDE.md that Claude should keep plan files in the repo until completion, it continuously ignores this.
What Should Happen?
It should allow us to persist plan files in our repo, in a plans folder. This helps keep context with the repo for plans that take a long time to complete.
Error Messages/Logs
Steps to Reproduce
Tell claude to update its claude.md that plans should be persisted in a plans folder in the repo.
Then ask it to make a plan in plan mode. The plan will not arrive in the plan folder, instead defaulting to the user home directory.
I recognise there are other similar issues but they don't cover this use case because with multiple markdown files in a monorepo, plans should be able to live in different locations depending on the context.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
Activity
github-actions commentedon Feb 17, 2026
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
andrewcamerongraham commentedon Feb 17, 2026
I recognise there are other similar issues but they don't cover this use case because with multiple markdown files in a monorepo, plans should be able to live in different locations depending on the context.
github-actions commentedon Mar 21, 2026
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
github-actions commentedon Mar 28, 2026
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.