What it does

Upload every frame plus a `manifest.json` to an Azure Blob Storage container under a timestamped prefix. Uses the native `@azure/storage-blob` SDK — authenticate with a connection string or account + key.

When to reach for it

Azure-native pipelines using workload deployments in AKS / App Service
Copy the connection string from portal Access keys — zero-config auth
Account + key mode for explicit credential management in CI

Install

npm i -g peepshow
npm i -g @azure/storage-blob

Use it

AZURE_CONTAINER=peepshow-archive \
AZURE_STORAGE_CONNECTION_STRING="DefaultEndpointsProtocol=https;AccountName=...;AccountKey=..." \
peepshow ./clip.mp4 --sink azure-blob

Make it automatic

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

Configuration

AZURE_CONTAINER Target container name. Must already exist. required
AZURE_PREFIX Prefix for every uploaded blob. Default `peepshow/`.
AZURE_STORAGE_CONNECTION_STRING Full connection string. Preferred when both modes are set.
AZURE_STORAGE_ACCOUNT Storage account name. Use with `AZURE_STORAGE_KEY`.
AZURE_STORAGE_KEY Storage account key.

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 Azure Blob Storage 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 AZURE_CONTAINER="..."

2. Register as an auto-sink

peepshow sinks add azure-blob
peepshow sinks add azure-blob --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 Azure Blob Storage sink forwards the run to the configured bucket / folder. Claude replies with a summary and a link to the created record.

The full transcript JSON is saved next to the frames in the manifest.

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

Azure Blob Storage — Upload frames and manifest to an Azure Blob container.