Your agents ship. You stay in the loop.
How it works
See it, say it, ship it, sign off.
- 01
Record
Narrate the bug in the app where it happens. Draw on the page. Every take lands on one timeline.
- 02
Route
Gripes arrive in one inbox and auto-file to the right project by the origin they were recorded on.
- 03
Fix
Your coding agent pulls the brief over MCP — transcript, keyframes, console errors — and opens the fix.
- 04
Sign off
A human reviews the before-video against the fix and approves.
SIGNED OFF
The artifact
What's in a gripe.
One folder, pushed as one unit. Everything a model needs to reproduce what you saw, and everything a reviewer needs to check the fix against it.
- rec-NN/walkthrough.webm
- the narrated screen recording
- rec-NN/frames/
- deduped keyframes, pointer marked
- transcript.txt
- on-device Whisper, timestamped
- console + network events
- captured while you spoke
- report.md
- authored for a model, not a human
Command line
Two commands, and it's wired in.
Push a gripe from anywhere
$ bun cli/push.ts ./gripes/2026-07-29-1215-walkthroughLet your agent pull the queue
$ claude mcp add inloop --env INLOOP_TOKEN=ilp_… -- bun cli/mcp.tsPricing