Plan mode: add a "save and exit" option that doesn't trigger implementation approval

Resolved 💬 2 comments Opened Jun 9, 2026 by jamespettinger Closed Jun 13, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Currently, ExitPlanMode is the only way to leave plan mode, and it always frames the outcome as "ready to implement - approve or reject?" This conflates two separate decisions: is the plan good? and do I want to implement it right now?

Proposed Solution

Proposed behaviour:

Add a second exit option - something like "Save plan and stop" ? that:

  • Writes/keeps the plan file
  • Exits plan mode
  • Does not show the implementation approval prompt

The existing "approve to implement" flow would remain unchanged for users who are ready to proceed immediately.

Alternative Solutions

Workaround today:

Call ExitPlanMode and manually reject the approval prompt. Works, but the UX implies intent to implement.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Use case:

Sometimes I just want to document a plan for future reference, review it asynchronously, or hand it off ? without being prompted to approve implementation immediately. The current flow makes plan mode feel like a commitment to act now, which discourages using it for exploratory or multi-session planning.

Additional Context

https://cursor.com/blog/plan-mode

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗