[BUG] Accepting ExitPlanMode with 'clear context' is treated as a rejection

Resolved 💬 3 comments Opened Mar 11, 2026 by tylerlaprade Closed Mar 15, 2026

Preflight Checklist

  • [x] I have searched existing issues and this has not been reported
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code

What's Wrong?

When accepting a plan via ExitPlanMode and choosing "clear context", Claude treats the acceptance as a rejection. It stays in plan mode and continues revising or asks for feedback, as if the plan was not approved.

This happens on the very first plan — no prior rejection is needed. The bug is specifically tied to the "clear context" option on acceptance.

Accepting without clearing context works fine.

Steps to Reproduce

  1. Enter plan mode (Shift+Tab or /plan)
  2. Claude generates a plan and calls ExitPlanMode
  3. Accept the plan and choose "clear context"
  4. Claude incorrectly treats the acceptance as a rejection — stays in plan mode, continues revising

Tested with bypassPermissions enabled; unclear if that's required for repro.

Expected Behavior

Accepting ExitPlanMode with "clear context" should exit plan mode and begin execution, same as accepting without clearing context.

What Should Happen?

The "clear context" option on plan acceptance should not change the approval signal that Claude receives. Clearing context should only affect the conversation history, not the plan approval state.

Is this a regression?

Yes — this was not an issue in earlier versions.

Claude Code Version

2.1.72

Claude Model

claude-opus-4-6

Platform

Anthropic API (Max subscription)

Operating System

macOS (Darwin 25.3.0)

Terminal/Shell

Ghostty / zsh

View original on GitHub ↗

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