Repository navigation
[BUG] Unintended Plan Regeneration After Plan Approval #2760
Description
Bug Description
I have created a plan and exited it to execute it. However I get another plan with the AI thinking like this:
Let me look at the Python code to understand how these are being used before I make a plan.
⏺ You're absolutely right about the cart operations being fragmented. Let me first understand how these GraphQL queries are being used in the Python code to give you a proper
analysis.
⏺ Task(Analyze cart tool implementations)
⎿ Done (15 tool uses · 39.9k tokens · 2m 56.1s)
✻ Thinking…
The user approved a plan, but that plan seems to be generated automatically or by another agent, and it's not exactly what I was planning based on my analysis. The user's
specific concerns were:
\
Environment Info
- Platform: darwin
- Terminal: cursor
- Version: 1.0.35
- Feedback ID: f187186f-f248-4188-8126-0af129f16302
Errors
[{"error":"Error: Command failed: security find-generic-password -a $USER -w -s \"Claude Code\"\nsecurity: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n\n at genericNodeError (node:internal/errors:983:15)\n at wrappedFn (node:internal/errors:537:14)\n at checkExecSyncError (node:child_process:882:11)\n at execSync (node:child_process:954:15)\n at TZ (file:///Users/vamshikodipaka/.nvm/versions/node/v22.15.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:700:3921)\n at file:///Users/vamshikodipaka/.nvm/versions/node/v22.15.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:622:9014\n at Q (file:///Users/vamshikodipaka/.nvm/versions/node/v22.15.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:526:17199)\n at VX (file:///Users/vamshikodipaka/.nvm/versions/node/v22.15.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:622:8160)\n at nS (file:///Users/vamshikodipaka/.nvm/versions/node/v22.15.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:622:7241)\n at f9 (file:///Users/vamshikodipaka/.nvm/versions/node/v22.15.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:622:11408)","timestamp":"2025-06-30T17:34:32.761Z"},{"error":"AbortError: The operation was aborted\n at abortChildProcess (node:child_process:716:27)\n at onAbortListener (node:child_process:786:7)\n at process.processTicksAndRejections (node:internal/process/task_queues:85:11)","timestamp":"2025-06-30T17:34:36.027Z"}]
Activity
[-]"Unintended Plan Regeneration After Plan Approval" This title captures the key technical issue of an unexpected plan being automatically regenerated after a user has already approved and attempted to exit a previous plan, suggesting a potential workflow o[/-][+][BUG] Unintended Plan Regeneration After Plan Approval[/+]github-actions commentedon Aug 16, 2025
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
github-actions commentedon Aug 20, 2025
This issue has been automatically closed as a duplicate of #2611.
If this is incorrect, please re-open this issue or create a new one.
🤖 Generated with Claude Code
github-actions commentedon Aug 27, 2025
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.