[MODEL]

Preflight Checklist

• [x] I have searched existing issues for similar behavior reports
• [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Claude refused a reasonable request

What You Asked Claude to Do

Feature Request: Allow Saving Work Before Context Compression in Plan Mode

Summary

Allow users to save/update documents with current context knowledge before context
compression, even when in plan mode.

Problem

When working in plan mode, Claude accumulates valuable findings and context.
When context runs low and compression is imminent:

1. User recognizes context is getting low
2. User asks Claude to stop current work and update a document with findings
3. Claude refuses: "I'm in plan mode, can't edit files"
4. Context gets compressed → knowledge/findings partially lost
5. Document is updated AFTER compression → incomplete information saved

Current Behavior

Plan mode restricts file editing operations. This restriction applies even when:

• User explicitly requests to save work
• Context compression is imminent
• Valuable findings would be lost

Expected Behavior

When user explicitly requests to save/update a document before context compression:

1. Claude should pause current plan mode work
2. Update the specified document with full context knowledge
3. Return control to user to decide next steps:

• Continue with plan mode work
• Exit plan mode
• Start fresh after compression

Use Case

Scenario: User is in plan mode researching a complex feature implementation.
After 30+ minutes of exploration, context is 80% full with valuable findings.

Current: User cannot save findings. Must wait for compression, losing detail.

Desired: User says "Stop and update NOTES.md with current findings" → Claude
saves everything → User can then decide to continue or restart.

Proposed Solution

Add an exception to plan mode file restrictions when:

1. User explicitly requests to save/preserve work, AND
2. Context is above a threshold (e.g., >70% full), OR
3. User uses a specific command like "emergency save" or "preserve findings"

Alternatively:

• Add a /save-plan command that works in plan mode
• Auto-prompt user to save when context reaches critical level

Impact

• Prevents loss of valuable research and findings
• Improves user experience during long planning sessions
• Reduces frustration when context compression occurs unexpectedly

Workaround

Currently, users must say: "Exit plan mode and write the current plan/findings to
[filename]" - but this requires knowing the workaround and loses plan mode state.

---

Submitted by: hermannakruse
Date: 2025-11-27
Platform: Windows / Claude Code CLI

---

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

What Claude Actually Did

Told me it can not write document in Plan mode.
Keept working until Context needed Compression.
Updated document after compression. Mabz losing informations.

Expected Behavior

Claude should have stop current work saving context for Updating Document. Telling me to change mode to be able to do update. Then offered to contiue work.

Files Affected

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Yes, every time with the same prompt

Steps to Reproduce

_No response_

Claude Model

Opus

Relevant Conversation

● Updated plan
  ⎿  /plan to preview · ~\.claude\plans\polished-honking-cherny.md

● Now let me update the implementation plan to use Option C:

● Updated plan
  ⎿  /plan to preview · ~\.claude\plans\polished-honking-cherny.md

> Plese update Like_vs_having with finding as context i lowering

● Updated plan
  ⎿  /plan to preview · ~\.claude\plans\polished-honking-cherny.md

● I'm in plan mode so I can only edit the plan file. Let me finalize the plan and include updating Like_vs_having.md
   as a step:

● Updated plan
  ⎿  /plan to preview · ~\.claude\plans\polished-honking-cherny.md
  ⎿  Interrupted · What should Claude do instead?

> How can i stop you. Plese update Like_vs_having.md bevore context ist lost.

 ▐▛███▜▌   Claude Code v2.0.55
▝▜█████▛▘  Opus 4.5 · Claude Max
  ▘▘ ▝▝    ~\GIT\hak\hak\ClaudWork\JustSimpleWork\Oracle\PlSqlTestEnviroment
══════════════════════════════════════ Conversation compacted · ctrl+o for history ═════════════════════════════════════
  ⎿  Read ..\..\..\..\..\..\..\.claude\plans\polished-honking-cherny.md (287 lines)
  ⎿  Read Like_vs_having.md (83 lines)
  ⎿  Read ..\..\..\..\..\..\EmilFrey-EFSAL-2788_hak\db\bereich-fw\test_ut3\run_weekly_tests.ps1 (333 lines)
  ⎿ Read ..\..\..\..\..\..\EmilFrey-EFSAL-2788\db\bereich-fw\test_ut3\rule_engine\ef_ts_pg_fz_rule_suite.pgs (230 lines)

  ⎿  Todo list read (5 items)

● I'll update Like_vs_having.md with the findings from the analysis. The plan file already captured the
  comprehensive analysis, but the user's original document needs updating.

● Update(Like_vs_having.md)
  ⎿  Updated Like_vs_having.md with 159 additions and 5 removals

Impact

Critical - Data loss or corrupted project

Claude Code Version

2.0.55 (Claude Code)

Platform

Other

Additional Context

_No response_