What it does

Open a Jira Cloud or Data Center issue with the peepshow run summary as the description and every frame uploaded as a multipart attachment. Supports basic auth (email + API token) or a PAT, and can target an existing issue key to append frames without creating a new one.

When to reach for it

Turn bug-report videos into properly-triaged Jira tickets automatically
Append follow-up clips to an existing issue via `JIRA_ISSUE_KEY`
Data Center / Server installs that need PAT auth instead of basic

Install

npm i -g peepshow

Use it

JIRA_BASE_URL=https://you.atlassian.net \
JIRA_USER=me@example.com \
JIRA_API_TOKEN=... \
JIRA_PROJECT_KEY=ENG \
peepshow ./bug-repro.mov --sink jira

Make it automatic

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

Configuration

JIRA_BASE_URL Atlassian instance URL, Cloud or Data Center. required
JIRA_USER Email for basic auth. Required with `JIRA_API_TOKEN`.
JIRA_API_TOKEN API token for basic auth.
JIRA_BEARER_TOKEN PAT — alternative to `JIRA_USER` + `JIRA_API_TOKEN`.
JIRA_PROJECT_KEY Project key for new issues. Required unless `JIRA_ISSUE_KEY` is set.
JIRA_ISSUE_KEY Attach to an existing issue; skip the create step.
JIRA_ISSUE_TYPE Issue type on create. Default `Task`.

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 Jira 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

# Add to ~/.zshrc, ~/.bashrc, or a project .env the agent can load
export JIRA_BASE_URL="..."

2. Register as an auto-sink

peepshow sinks add jira
peepshow sinks add jira --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 Jira sink 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'.

Jira — File a Jira issue with every frame as an attachment.