Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Plan mode docs missing prompt-based plan filename behavior [1 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#49297•Fetched 2026-04-17 08:45:15
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

plansDirectory and plan-file storage/editing behavior

Current Documentation

The docs currently say:

| plansDirectory | Customize where plan files are stored. Path is relative to project root. Default: ~/.claude/plans |

And the plan workflow docs say:

Press Ctrl+G to open the plan in your default text editor, where you can edit it directly before Claude proceeds.

These pages establish that plan files are stored on disk and can be opened in an editor, but they do not explain how Claude names those files.

What's Wrong or Missing?

Changelog v2.1.111 says: Plan files are now named after your prompt (e.g. fix-auth-race-snug-otter.md) instead of purely random words.

The current docs explain where plan files live and that you can open/edit a plan, but they do not document that plan filenames now include prompt-derived words rather than being composed only of random words. That leaves users without guidance on how to find the right plan file in plansDirectory, recognize why filenames changed, or script around the new naming behavior.

Suggested Improvement

Add a short note anywhere plan files are described (at minimum near plansDirectory, and ideally also in the plan workflow docs) that explains the filename convention.

Suggested content outline:

Plan filenames now include words derived from the prompt instead of using only random-word names. For example, a plan for "fix auth race" may produce a filename like fix-auth-race-snug-otter.md.

It would also help to clarify that plansDirectory changes where plan files are stored, while the filename itself is generated by Claude Code.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/settingsplansDirectory explains where plan files are stored
https://code.claude.com/docs/en/common-workflowsPlan mode workflow tells users they can open and edit the plan in an external editor
https://code.claude.com/docs/en/best-practicesRepeats the external-editor workflow for plans
https://code.claude.com/docs/en/claude-directoryLists ~/.claude/plans/ as a local data directory

Total scope: 4 pages affected

Source: Changelog v2.1.111

Exact changelog entry: Plan files are now named after your prompt (e.g. fix-auth-race-snug-otter.md) instead of purely random words

extent analysis

TL;DR

Update the documentation for plansDirectory and plan workflow to include information about the new filename convention for plan files, which now includes words derived from the prompt.

Guidance

  • Review the suggested content outline provided in the issue to understand the required documentation changes.
  • Update the documentation pages listed in the Affected Pages section to reflect the new filename convention.
  • Consider adding a note to clarify that plansDirectory changes the storage location of plan files, while the filename itself is generated by Claude Code.
  • Verify that the updated documentation accurately reflects the current behavior of the system.

Example

No code snippet is necessary for this issue, as it is related to documentation updates.

Notes

The issue is specific to updating documentation to reflect a change in the system's behavior, and the suggested improvement provides a clear outline of the required changes.

Recommendation

Apply workaround: Update the documentation to reflect the new filename convention, as this will provide users with the necessary information to understand the system's behavior.

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…
#SSR setup#ISR setup#authentication setup#request error#file not found

Still need to ship something?

×6

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

Back to top recommendations

TRENDING