peepshow/ sinks/ continue

Reel #61 Editor integration

peepshow sink / continue

ContinueFrames + manifest into Continue's workspace context folder.

Drop frames, `manifest.json`, and (optionally) `transcript.md` into `.continue/context/` so the next Continue prompt has the whole clip as context.

drop · process · continue

What it does

Write the extracted frames into Continue's workspace context directory (`.continue/context/peepshow/` by default) as real files — not symlinks — so Continue's strict file walker picks them up on the next prompt. Alongside the frames, `manifest.json` gives the model structured video/audio metadata, and when transcription is enabled `transcript.md` lands as a timestamped markdown file Continue can search.

When to reach for it

  • Use Continue inside VS Code / JetBrains and want every peepshow run to become automatic context
  • Agents that route video context to Continue instead of a chat upload
  • Keep the full timeline — frames, metadata, and transcript — in one folder Continue already watches

Install

npm i -g peepshow

Use it

peepshow ./demo.mp4 --sink continue

Make it automatic

Register the sink once — every run fires it afterward. Scope by --when so it only runs for matching videos.

peepshow sinks add continue
peepshow sinks add continue --when extension=mp4,mov
peepshow sinks add continue --when path=/Volumes/Work/

Configuration

  • CONTINUE_CONTEXT_DIR Target directory. Default `./.continue/context/peepshow/`. Relative paths resolve against `cwd`.
  • PEEPSHOW_CONTINUE_DIR Alias for `CONTINUE_CONTEXT_DIR`; wins when both are set.
  • CONTINUE_COPY_MODE `copy` · `symlink` · `link` (hardlink). Default `copy`. Hardlink falls back to copy across filesystems.

Use with an LLM agent

Every peepshow sink reads its config from env vars and receives a single JSON payload on stdin. An LLM agent (Claude Code, Cursor, Windsurf, Gemini, Codex) can drive the Continue sink automatically when three things are true:

  • the env vars below are exported in the agent's shell (or a project .env it can load),
  • the peepshow CLI is on PATH — install with npm i -g peepshow,
  • a peepshow auto-sink is registered for the run (optional but recommended — makes invocation zero-argument).

1. Set the environment

This sink has no required env vars — it writes to a local path. Pass the destination via --sink-arg:

peepshow ./demo.mp4 --sink continue

2. Register as an auto-sink

peepshow sinks add continue
peepshow sinks add continue --when extension=mp4,mov

3. Example LLM session

You → drop a .mov into Claude Code.

Claude → auto-invokes /peepshow:slides ./clip.mov. peepshow extracts frames + audio, the Continue sink forwards the run to the configured Continue target. Claude replies with a summary and a link to the created record.

The transcript rides along in the payload whenever the audio pass transcribes successfully.

Write your own

A sink is any executable that reads the --emit json payload on stdin. Shell, Node, Python, Go — the spec's in docs/PLUGINS.md. Register persistent ones with peepshow sinks add-cmd 'your-command'.