Skip to content

[BUG] Claude consistently ignores being directed to store plan files in the repo #26226

Closed as not planned

Description

@andrewcamerongraham

Preflight Checklist

  • 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.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.42

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Using latest vscode plugin as well.

Activity

  1. github-actions commented on Feb 17, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. Project-level plansDirectory setting not respected #18623
    2. [BUG] vscode Plan mode saves files to system directory instead of project directory #14186
    3. Project-level plansDirectory setting ignored in favor of global default #19537

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. andrewcamerongraham commented on Feb 17, 2026

    @andrewcamerongraham
    Author

    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.

  3. github-actions commented on Mar 21, 2026

    @github-actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  4. github-actions commented on Mar 28, 2026

    @github-actions

    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.

  5. locked as resolved and limited conversation to collaborators on Mar 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingstaleIssue is inactive

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions