ClipFix Download

macOS & Windows · Free · Open source

Record the bug.
Paste the fix context.

ClipFix turns a short screen recording into annotated keyframes and a structured brief your coding agent can actually use. Stop describing bugs. Show them.

Free & open source · macOS 13+ and Windows 10/11

Notes
Save
Q2 planning
01 Note open
Notes
Save
Note title
02
02 Title focused
Notes
Save
Q3 launch retro
03✕ disabled
03 Save still off
Notes
Save
Q3 launch retro
04✓ enabled
04 Save flips on

⟶ annotated keyframes, extracted automatically

The workflow

Three steps, about two minutes

01

Record

Hit ⌃⌘RCtrl+Alt+R or click the menu-barsystem-tray icon and capture the bug, the broken layout, the thing that’s hard to describe.

02

Analyze

ClipFix pulls the keyframes that matter, annotates what changed in each, and Gemini Flash writes a structured brief — usually in under 30 seconds.

03

Paste

Copy the brief into Cursor, Claude Code, or Codex. No reformatting. The input your agent actually needs.

The output

This is what your agent receives

Not a video file. Not a vague description. A structured brief — annotated keyframes, reproduction steps, and a pointer at the likely cause — formatted for an agent to reason about.

Try it: copy the brief and paste it into your editor.

clipfix-brief.md
Notes
Save
Note title
01
01Title focused
Notes
Save
Q3 launch retro
02✕ disabled
02Typed — Save off
Notes
Save
Q3 launch retro
03✓ enabled
03Body edit — Save on
## Bug: Save button stays disabled after editing the title

**Steps to reproduce**
1. Open a note and click into the title field
2. Type a new title
3. The "Save" button stays greyed out

**Expected:** Save enables as soon as the title changes.
**Observed:** Save only enables once you also edit the body.

**Keyframes**
- [01] title field focused
- [02] new title typed — Save still disabled
- [03] body edited — Save becomes active

**Likely area:** the form's dirty-state watcher only tracks the body field, not the title.

Why ClipFix

A recording is pixels.
Your agent needs context.

Drop a raw clip into a coding agent and it guesses. The frames that matter are buried; nothing is labeled. Building that context by hand is slow — so most people skip it, and the fix misses. ClipFix does the extraction and annotation for you, every time.

Bring your own key

Keyframes analyzed through your own Gemini API key — no ClipFix middleman.

Open source

FOSS, MIT-spirited. Inspect it, fork it, ship it.

Agent-native

Output formatted for Cursor, Claude Code, Codex & friends.

Questions

Frequently asked

What does ClipFix produce from a screen recording? +

Two things: annotated keyframes showing what changed on screen, and a concise instruction brief — plain text you paste directly into Cursor, Claude Code, Codex, or any multimodal coding agent.

Does ClipFix upload my recordings to the cloud? +

Not to any ClipFix cloud — there is none. ClipFix is bring-your-own-key: the keyframes it extracts are sent to the Google Gemini API using your own API key, so they go to your Gemini account, not our servers, and we never see or store them. The full video file is never uploaded — only the extracted keyframes.

How do I use it with Cursor or Claude Code? +

Record, wait for analysis (typically under 30 seconds), then copy the generated brief and paste it into your Cursor composer or Claude Code session. The brief is already structured for agent consumption — no reformatting needed.

What does ClipFix cost? +

ClipFix is free and open source. Analysis uses the Gemini Flash API, which has a free tier of about 20 requests per day. Paid usage is roughly $0.0003 per second of recording — about four cents for a two-minute clip.

Which platforms and versions are supported? +

macOS 13 Ventura or later (Apple Silicon and Intel) and Windows 10 and 11. Recording uses each platform’s native screen capture — ScreenCaptureKit on macOS, native graphics capture on Windows.