Clipy

Clipy is a screen recorder for coding agents. Use it to show a UI bug, explain a design change, or walk through client feedback. Your team gets a playable video; a connected coding agent can retrieve the recording’s available narration and visual context.

Follow the agent setup guide once, then paste a normal Clipy video link into your agent session. Wait for processing and ask the agent to summarize the requested change and any missing evidence before it edits your code. The skill reads accessible links; authenticated MCP tools also support library workflows.

Depending on what was captured and processed, context can include a summary, timestamped narration, relevant frames, and pointer or interaction evidence. Microphone, system audio, and pointer capture depend on your recorder, browser, and selected source. A silent recording has no spoken transcript; missing pointer data does not mean no click happened. Context access follows the recording’s access rules. Anyone with an unrestricted public link can open it, so check access before sharing.

A screenshot is often enough for one visible layout issue. A recording is useful when the order of actions, a changing state, or spoken feedback matters. Neither establishes the technical cause by itself. Your coding agent still needs the relevant repository and checks for the intended behavior.

Yes. Clipy is free to start with a 7-day free trial, no card needed. After the trial, recording requires Pro at $9 per month. Existing recordings remain playable and downloadable. You sign in to save and share; viewers of unrestricted public links do not need an account.

Clipy has everything Jam has, and more. Like Jam, it captures a bug in Chrome with its console errors and failed network requests attached. A Clipy link also gives a person or a coding agent the evidence, a transcript of what you said and key-moment frames with no account. And where Jam records the web, Clipy's Mac and Windows apps also record native apps, terminals and simulators.