What it does
[Plane](https://plane.so) is the open-source project-management tool teams pick when they want a Linear / Jira workflow without the SaaS lock-in. This sink files one work item per peepshow run against `POST <baseUrl>/api/v1/workspaces/<workspaceSlug>/projects/<projectId>/issues/` with a JSON body of `{name, description, priority}`. The work-item name is `peepshow: <title>` (truncated to Plane's 255-char cap), the description is a flat metadata block plus the transcript when present, and priority defaults to `medium` — override with `PLANE_PRIORITY=urgent|high|low|none|null`. Auth uses a personal API token (Settings → API tokens) sent as both the `x-api-key` header (Plane's native scheme) and a standard `Bearer` for proxies that expect OAuth-shaped headers.
When to reach for it
- Auto-file a QA / bug-report work item every time an agent watches a recording on a Plane-tracked project
- Keep a stakeholder-visible audit trail of every video an LLM has reviewed alongside the human-filed issues
- Bridge peepshow into Plane workflows (assignees, cycles, modules) without writing a custom Webhook handler
Install
npm i -g peepshowUse it
PLANE_API_TOKEN="plane_api_xxxxxxxxxxxxx" \
PLANE_WORKSPACE_SLUG="acme" \
PLANE_PROJECT_ID="11111111-2222-3333-4444-555555555555" \
peepshow ./bug-repro.mp4 --sink planeMake it automatic
Register the sink once — every run fires it afterward. Scope by --when so it only runs for matching videos.
peepshow sinks add plane
peepshow sinks add plane --when extension=mp4,mov
peepshow sinks add plane --when path=/Volumes/Work/Configuration
PLANE_API_TOKENPersonal API token (sent as Bearer + x-api-key). Generate at Workspace Settings → API tokens. requiredPLANE_WORKSPACE_SLUGWorkspace slug — the path segment in your Plane URL (e.g. `acme`). requiredPLANE_PROJECT_IDProject UUID — find it under Project Settings → General. requiredPLANE_API_URLBase URL of the Plane API. Default `https://api.plane.so`; override for self-hosted instances.PLANE_PRIORITYIssue priority. One of `none|urgent|high|medium|low|null`. Default `medium`.
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 Plane sink automatically when three things are true:
- the env vars below are exported in the agent's shell (or a project
.envit can load), - the
peepshowCLI is onPATH— install withnpm i -g peepshow, - a peepshow auto-sink is registered for the run (optional but recommended — makes invocation zero-argument).
1. Set the environment
# Add to ~/.zshrc, ~/.bashrc, or a project .env the agent can load
export PLANE_API_TOKEN="..."
export PLANE_WORKSPACE_SLUG="..."
export PLANE_PROJECT_ID="..."2. Register as an auto-sink
peepshow sinks add plane
peepshow sinks add plane --when extension=mp4,mov3. Example LLM session
You → drop a
.movinto Claude Code.Claude → auto-invokes
/peepshow:slides ./clip.mov. peepshow extracts frames + audio, thePlanesink forwards the run to a new issue with the frames attached. Claude replies with a summary and a link to the created record.
Transcript appears in the issue body, giving triage a copy-paste-able record of what was said.
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'.