marp-preview

A live Marp slide preview in a Claude Code pane: every slide rendered in one scrolling column, re-rendered on save and scrolled to the slide Claude or your editor just changed.

Usage, requirements and troubleshooting: github.com/nogu66/marp-preview.

What the hooks do

The plugin is one hooks module, hooks/register.tsx:

| Hook | What it does | | --- | --- | | session.start | Registers the /marp command, and resumes following the deck if the pane is still open after a reload | | command.run (/marp) | Finds or takes the deck, opens the pane and starts marp watching it | | ui.render (the pane) | Draws every slide's image in one column, which the pane scrolls | | ui.close | Stops marp when the pane closes | | session.end | Stops marp when the session ends (not on a /clear, which keeps the pane) |

What it touches

• Files it reads: the deck you open, and its modification time once a second while the pane is open, to see that marp is keeping up. To find a deck when /marp has no argument it runs grep for marp: true over the .md files under the folder the session is in, then over the project.
• Files it writes: none in the project. It never changes the deck.
• Processes it runs: marp (from a node_modules at or above the deck, else npx --yes @marp-team/marp-cli) with --watch --images png --allow-local-files, writing PNGs under /tmp/marp-preview/. It is one long-running process, with the browser marp starts, for as long as the pane is open: started by /marp, restarted if it dies or hangs, and ended when the pane closes, the session ends or the plugin reloads. Also the grep above.
• Not touched: the network (beyond what npx does to fetch marp-cli), the model, tool calls, the prompt, and settings.
• Environment variables: none.