claude-code - 💡(How to fix) Fix Plan pickup is BROKEN. You told users a new session resumes. It DOESN'T. [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#54720Fetched 2026-04-30 06:37:53
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4
RAW_BUFFERClick to expand / collapse

THE LIE

Claude told me: "close this session, start a fresh one, it picks up — the plan is saved to disk."

It DIDN'T. Fresh session ignored the saved plan. Defaulted to git log and a stale handoff doc. Reported "nothing pending."

I lost the work. I lost the time. I lost $200/mo of trust. F**K Y*U.

WHERE THE PLAN ACTUALLY WAS

~/.claude/plans/<random-slug>.md

Random slug. No project link. No timestamp. No manifest. The fresh session has ZERO documented way to know that file belongs to my cwd.

Your own harness wrote it. Your own model can't find it.

THE BROKEN CONTRACT

Telling a paying user "close the session, the next one resumes" is a PROMISE. You DON'T keep it. Failure is SILENT — the model says "nothing to do" while the plan sits one directory away.

Silent wrong is WORSE than loud wrong.

FIX IT

Pick one. ANY of these works:

(a) Save plans to the PROJECT's .claude/plans/ — co-located, discoverable. (b) Inject the latest plan path into the next session's system context. The harness ALREADY KNOWS the cwd → project mapping. (c) Auto-load ~/.claude/plans/<latest-by-mtime>.md alongside MEMORY.md. (d) At MINIMUM, document the pickup protocol in the system prompt so the model checks the right paths before falling back to git.

You're already doing (c) for MEMORY.md. Do it for plans. It's ONE LINE.

REPRO

  1. Approve a plan via ExitPlanMode.
  2. End session.
  3. Fresh session, same cwd. Say "pick up last session."

Expected: resumes. Actual: "nothing pending."

ENV

  • Claude Code, Windows 11
  • Model: claude-opus-4-7[1m]
  • Plan file: ~/.claude/plans/streamed-purring-mist.md (~300 lines, approved)

WHAT I WANT

Stop telling users to close sessions until pickup works. Make the harness surface what the harness saves. Each release feels like a downgrade. FIX IT.

extent analysis

TL;DR

Save plans to the project's .claude/plans/ directory or implement one of the suggested alternatives to ensure seamless session pickup.

Guidance

  • The issue arises from the plan file being saved to a non-project-specific location (~/.claude/plans/) without a clear link to the project, making it undiscoverable by the model in a fresh session.
  • To verify the issue, reproduce the steps provided in the REPRO section and observe the model's behavior when attempting to pick up the last session.
  • Consider implementing one of the suggested fixes, such as saving plans to the project's .claude/plans/ directory or auto-loading the latest plan file alongside MEMORY.md.
  • The harness already knows the cwd → project mapping, which could be utilized to inject the latest plan path into the next session's system context.

Example

No code snippet is provided as the issue does not explicitly mention specific code or APIs.

Notes

The provided information suggests that the issue is related to the plan file's location and the model's inability to discover it in a fresh session. The suggested fixes aim to address this issue by making the plan file more discoverable or by modifying the model's behavior to automatically load the latest plan.

Recommendation

Apply workaround (a) by saving plans to the project's .claude/plans/ directory, as this seems to be the most straightforward solution that addresses the root cause of the issue.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Plan pickup is BROKEN. You told users a new session resumes. It DOESN'T. [1 participants]