### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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? The latest VSCode extension now shows the Planning Mode plan as: Claude‘s Plan.md (vdn3z6) instead of displaying inline. This is harder to read than the

[BUG] Claude‘s Plan.md (vdn3z6)

Status Fixed / completed

Maintainer reply ✓ Yes — hackyon-anthropic

Activity 5 comments · opened Oct 1, 2025 · closed Oct 7, 2025

💡 Likely answer: A maintainer (hackyon-anthropic, collaborator) responded on this thread — see the highlighted reply below.

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?

The latest VSCode extension now shows the Planning Mode plan as:
Claude‘s Plan.md (vdn3z6) instead of displaying inline.

This is harder to read than the previous version.

What Should Happen?

It would be substantially better if the filename ended with the .md extension.
Claude‘s Plan (vdn3z6).md

Then it can be saved and viewed with the Markdown Preview extension. 1000% easier to digest.

Error Messages/Logs

Steps to Reproduce

ask for a plan

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

2.0.0

Claude Code Version

0.2.21

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

5 Comments

orijins-abundance · 11 months ago

Similar issue here (VSCode extension anthropic.claude-code v2.0.1), used inside Windsurf.

Plan shows as an unstyled markdown file:
<img width="729" height="434" alt="Image" src="https://github.com/user-attachments/assets/9eb8d111-7097-4541-a044-911ca4843b8a" />

Windsurf version info:

Windsurf Version: 1.12.12
Windsurf Extension Version: 1.48.2
Windsurf Commit: 146732d0c28fe6d8f982f1ebf7ab4101ece88c63
VSCode OSS Version: 1.99.3
Commit: 146732d0c28fe6d8f982f1ebf7ab4101ece88c63
Date: 2025-09-29T13:08:25.200Z (3 days ago)
Electron: 34.4.0
ElectronBuildId: undefined
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

bruno-git · 11 months ago

I'm experiencing the same issue. The plan file opens as raw markdown source in a readonly temp file (/temp/readonly/Claude's Plan.md), which makes it difficult to read with all the markdown syntax visible (##, **, etc.).

Current behavior:

Plan opens in /temp/readonly/Claude's Plan.md (random_id)
No markdown preview available (Ctrl+Shift+V doesn't work)
Must read raw markdown with formatting symbols

Desired behavior:

Plan should render with proper markdown formatting (headings, bold, lists, etc.)
Either force markdown preview mode on open, or make the file previewable

This significantly impacts readability when Claude presents complex multi-step plans. Having to mentally parse markdown syntax while reviewing technical plans adds unnecessary cognitive load.

Would appreciate if this could be prioritized - it's a common workflow issue that affects every planning session.

precisionpete · 11 months ago

Just to reiterate, I think the problem is as simple as the .md extension appearing in the middle of the file name. The IDE does not know what to do with it. If you just add the .md to the end of the name, it would work.

Calude's Plan.md (12345) --> Calude's Plan (12345).md

hackyon-anthropic collaborator · 10 months ago

We've heard the feedback from our users, and we've moved the plan to the side panel instead in the latest update. Please update and give it a spin when you get the chance!

github-actions[bot] · 10 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.