Cursor — Project-level rules auto-load when peepshow is installed.

How it plugs in

Cursor picks up `.cursor/rules/peepshow.mdc` automatically on any project that contains the peepshow extension repo. The rule tells the agent: when the user references a video, run `peepshow <path>` before answering.

Install

# inside your project:
git clone --depth 1 https://github.com/t0mtaylor/peepshow.git .peepshow-ref
# Cursor auto-picks up .cursor/rules/ — no restart.

# OR globally via npm:
npm i -g peepshow
# then symlink / copy .cursor/rules/peepshow.mdc into your repo.

Files involved

• .cursor/rules/peepshow.mdc Auto-loaded rule describing peepshow usage.

In practice

# In the Cursor agent chat:
user: what happens in demo.mp4?
agent: (runs peepshow ./demo.mp4 --emit json) → answers with frames

All 95 sinks still work

The CLI is the same across agents — which means every sink documented under /sinks is available here. Auto-sinks fire regardless of which agent invoked peepshow.

Report + LLM analysis loop

Every run also writes a self-contained report.html + manifest.json next to the frames (see the Report page). When Cursor consumes the frames, the analysis flows back into the report so whoever opens it next sees the model's understanding without re-running the prompt.

echo '{"summary":"<your summary>","provider":"cursor"}' \
  | peepshow report annotate "<outputDir>"

The annotate instruction is wired into the Cursor integration — the agent runs it after reading the frames + transcript. Report walkthrough →