Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Plan mode docs omit `/plan open` and existing-plan reuse 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#52624•Fetched 2026-04-24 06:02:09
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/commands

Section/Topic

/plan command reference and the workflow for reopening or continuing an existing plan

Current Documentation

The docs currently say:

/plan [description] — "Enter plan mode directly from the prompt. Pass an optional description to enter plan mode and immediately start with that task, for example /plan fix the auth bug"

"Enter plan mode by pressing Shift+Tab or prefixing a single prompt with /plan."

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

plans/ — "Plan files written during plan mode"

No page under https://code.claude.com/docs/en/ currently documents /plan open or explains how entering plan mode should behave when an existing plan file is already present.

What's Wrong or Missing?

Changelog v2.1.119 includes this entry:

Fixed /plan and /plan open not acting on the existing plan when entering plan mode

That reveals a user-facing workflow the docs do not currently explain:

A. /plan open is undocumented

The command reference documents /plan, but not /plan open.

B. Existing-plan behavior is undocumented

The docs explain how to enter plan mode and where plan files are stored, but they do not explain that Claude Code can reopen or continue working against an existing plan when you enter plan mode again.

Users who see saved plan files, customize plansDirectory, or encounter /plan open have no documentation telling them how this workflow is supposed to work.

Suggested Improvement

Add a short plan-resume subsection to the command and plan mode docs that covers:

  1. /plan open syntax and purpose
  2. What /plan does when a relevant existing plan already exists
  3. How this interacts with plansDirectory / ~/.claude/plans
  4. Any selection rules or prompts Claude Code uses when multiple saved plans are available

At minimum, the /plan command reference should mention that Claude Code can act on an existing plan, and /plan open should appear anywhere other slash commands are documented.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageLine(s)Context
https://code.claude.com/docs/en/commands63Documents /plan [description], but /plan open is absent
https://code.claude.com/docs/en/permission-modes127-147Explains how to enter and exit plan mode, but not how existing plans are reopened or reused
https://code.claude.com/docs/en/settings207Documents plansDirectory without explaining how users reopen a saved plan from that directory
https://code.claude.com/docs/en/claude-directory1471-1477Mentions ~/.claude/plans/ as plan storage, but not the user workflow for opening those plans

Total scope: 4 pages affected

Source: Changelog v2.1.119

Exact changelog entry:

Fixed /plan and /plan open not acting on the existing plan when entering plan mode

extent analysis

TL;DR

Update the documentation for the /plan command to include information on /plan open and how Claude Code handles existing plans.

Guidance

  • Add a new subsection to the command and plan mode docs to cover /plan open syntax, purpose, and behavior with existing plans.
  • Update the /plan command reference to mention its ability to act on an existing plan.
  • Clarify how plansDirectory and ~/.claude/plans interact with the plan reopening workflow.
  • Consider adding information on selection rules or prompts used when multiple saved plans are available.

Example

No code snippet is necessary for this documentation update.

Notes

The exact wording and structure of the new documentation will depend on the existing style and tone of the Claude Code documentation.

Recommendation

Apply workaround: Update the documentation to include the missing information, as this will directly address the issue of unclear workflow for reopening or continuing an existing plan.

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…
#agent execution#callback error#memory management#API rate limit#retriever error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING