What it does

Flatten each peepshow run into a single wide structured event and POST it to a Honeycomb dataset. Dotted keys (`video.duration_seconds`, `video.tags.director`, `audio.transcript_segment_count`, …) populate columns automatically — no dataset schema to maintain. US + EU regions supported, with a full `HONEYCOMB_API_URL` override for on-prem / proxied deployments.

When to reach for it

Query peepshow runs alongside your app telemetry in Honeycomb
Pass arbitrary container tags through as `video.tags.<key>` columns
EU-region Honeycomb: set `HONEYCOMB_REGION=eu`

Install

npm i -g peepshow

Use it

HONEYCOMB_API_KEY=... \
HONEYCOMB_DATASET=peepshow \
peepshow ./trigger.mp4 --sink honeycomb

Make it automatic

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

Configuration

HONEYCOMB_API_KEY `X-Honeycomb-Team` header. required
HONEYCOMB_DATASET Dataset name (URL-encoded into the path). required
HONEYCOMB_REGION `us` (default) | `eu`. Unknown values clamp to `us`.
HONEYCOMB_API_URL Full API base override (on-prem / proxied).

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 Honeycomb 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 HONEYCOMB_API_KEY="..."
export HONEYCOMB_DATASET="..."

2. Register as an auto-sink

peepshow sinks add honeycomb
peepshow sinks add honeycomb --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 Honeycomb sink forwards the run to the alert / incident stream. Claude replies with a summary and a link to the created record.

Transcript metadata (language, duration, silence ratio) tags each event.

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'.

Honeycomb — Ingest every peepshow run as a structured Honeycomb event.