Feature request: extend plan-mode's inline-comment review UI to arbitrary markdown files
Plan mode (in the VS Code extension) lets you highlight a portion of the rendered plan and attach an inline comment before approving — feedback anchored to the exact spot it applies to, rather than describing the location in prose back in chat.
It'd be valuable to have that same interaction available for any markdown file Claude is iterating on with you, not just plan-mode's plan artifact. Concretely: a long-form document (e.g., a Method-section draft, a design doc, a research writeup) evolves over a long session through many rounds of feedback. Right now the only ways to give spot-specific feedback are:
- Quote the passage back in chat and describe where it is (works, but loses the direct "point at this exact spot" precision)
- Manually type an inline marker/comment into the file yourself and ask Claude to look for it (works today with zero new tooling, but requires opening the file in an editor and typing the marker by hand — no real UI gesture)
Neither is as fast as the plan-mode experience. A general "annotate this file" mode — even scoped to files Claude just wrote/is actively editing in the session — would remove a lot of friction for iterative document work that isn't code implementation planning (specs, research writeups, decision records, etc.).
3 Comments
@melissarobertson1119 A workaround I've been using: a skill that borrows the Claude Code extension's plan panel.
<img width="1498" height="1027" alt="Image" src="https://github.com/user-attachments/assets/fd0e2634-42e0-4b1e-b0db-0e228fad1174" />
To use it:
or
/manage-md-comments openwith the.mdfile already open in the editor.It loads the
.mdinto the panel verbatim, so you're commenting on the real document. The comments come back, get folded into a working revision, and the revised document is re-presented for another pass. You loop until it's settled. The file on disk is updated when you approve the plan, since plan mode blocks edits until then.It needs the VS Code extension: a terminal session has no comment affordance.
The gist also includes an optional VS Code snippet for the second case you describe, typing a marker by hand:
ac+ Tab expands to a> 💬 **AC:**blockquote, which stays visible in the rendered markdown preview.Gist: https://gist.github.com/yulissateran/6404fdda5fee9b319c0a2cf03749b59b
To install, save the two files as:
The directory name and the
SKILL.mdfilename both matter, or the skill won't load. Restart the session afterwards.It's been good enough for iterating interactively on specs, docs, and research. Native comments would beat it, but in the meantime I hope it helps!
for files that do not require a preview, I found this shortcut useful:
Alt+KorOption+K, auto writes the selection lines to the extension and moves the cursos there, so you start typing without manual copy/past<img width="1003" height="148" alt="Image" src="https://github.com/user-attachments/assets/96db781a-4fbd-47aa-a077-ea7f67be5411" />
I wanted the same thing, so I built a mod for it. It's called Lazy Panda Panel.
It opens a file inside Claude Code, right in the terminal, no VS Code needed. You click or drag over the part you want changed, type a comment, and add as many as you like. Then you send them all at once. Claude edits the real file and the pane shows what changed.
It works on Markdown, and also Word, Excel, PDF, HTML and Confluence files, because that's mostly what I get Claude to make at work.
Then
/panda yourfile.md.https://github.com/paragpandyareal/lazy-panda-panel
It's free and open source. Still early days, so if you try it I'd really like to hear what breaks or feels clunky.