[BUG] Plan output in terminal shows only headers, not full content

Resolved 💬 5 comments Opened Jan 12, 2026 by yrashk Closed Feb 27, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When Claude creates a plan file, the terminal output sometimes shows only the section headers (skeleton), but the actual plan file contains the complete content.

This is sporadic behavior - it doesn't happen every time. My CLAUDE.md instructions tell Claude to use XML tags for structuring plans. This may be relevant to reproducing the issue, as the XML content appears to be stripped from the terminal display.

Terminal shows only headers with no content:

Plan saved to: ~/.claude/plans/example-plan.md
Plan: Implement Feature X

Context

Requirements

Implementation Steps

Files to Modify

Verification

However, opening the actual file reveals the complete plan with full content under each section (XML-structured content in my case).

What Should Happen?

Terminal output should show the actual plan content, or at least indicate that content exists under each header.

Error Messages/Logs

N/A

Steps to Reproduce

  1. Add instructions to CLAUDE.md telling Claude to use XML tags for structuring plans
  2. Start Claude Code in plan mode
  3. Have Claude create a plan
  4. Observe the terminal output - sometimes only headers are shown while the file has full content

Claude Model

Opus

Is this a regression?

Unknown

Last Working Version

_No response_

Claude Code Version

2.1.5

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Ghostty/fish

Additional Information

This is confusing because users see an apparently empty plan in the terminal, making it look like the plan generation failed or produced no useful output. Users have to manually open the file to see the actual plan.

View original on GitHub ↗

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