[FEATURE] Plans vanish when declining tool use

Resolved 💬 5 comments Opened Jan 10, 2026 by vivere-dally Closed Feb 24, 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

I often start with a planning session. After we get to have an idea on what to implement, Claude makes a very nice summary and prompts me: 1) start implementation 2) same as (1) but auto-accept and then 3) propose something else (Tool rejection).

I often reject with something like "hey, please dump this nice wall of text you returned into a markdown file", so I can have it outside of the claude flow (i know it has some inner plans or whatever, but I want to get that wall of text into my filesystem.

As I reject it, it then spends an intolerable amount of time to produce that md file (and also more tokens - for what - it already has the text, just dump it into a file). When I get the plan, it often seems worse than the wall of text I got initially. Moreover, the wall of text disappears from the history. Why?

Proposed Solution

When exiting the plan mode, do not prompt with only 3 options, add a fourth: "Save plan to disk"

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

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