[BUG] Plan files don't consistently open in review mode with inline comments in VS code extension

Resolved 💬 3 comments Opened May 8, 2026 by sIlENtbuffER Closed May 11, 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 I manually open a plan file from the VSCode sidebar, it opens as plain markdown without the inline comment capability. The automatic trigger that opens plans in "review mode" (where inline comments work) only works inconsistently. There is no way to manually open a plan file in review mode or convert a plain markdown plan into review mode after opening.

What Should Happen?

According to the official documentation:

"In Plan mode, Claude describes what it will do and waits for approval before making changes. VS Code automatically opens the plan as a full markdown document where you can add inline comments to give feedback before Claude begins."

Plan files should always open in review mode with inline comment capability, whether opened automatically by the trigger or manually from the sidebar. Alternatively, there should be a command (e.g., "Claude Code: Open Plan in Review Mode") to manually trigger review mode.

Error Messages/Logs

Steps to Reproduce

Set modes to "plan" in a new chat in VSCode extension anthropic.claude-code
Ask Claude to create a plan
Instead of clicking the automatically-opened plan, manually open the plan file via the VSCode sidebar (sometimes it won't automatically open)
Open the plan file
The file opens as plain markdown - no inline comment capability available
There is no command or method to convert it to review mode

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.34 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

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