ClipFix Download

macOS · 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.

01 Bug trigger
02 Error state
03 Cursor
04 Expected

⟶ annotated keyframes, extracted automatically

The workflow

Three steps, about two minutes

01

Record

Hit ⌃⌘R or click the menu-bar 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
01Title focused
02Typed — Save off
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.

Local-first

Recordings never leave your Mac. Only keyframes are analyzed.

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? +

No. Your recordings stay on your machine. Only the extracted keyframes are sent to the Gemini Flash API for analysis — the video itself never leaves your Mac.

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 macOS versions are supported? +

macOS 13 Ventura or later, for screen recording via ScreenCaptureKit. Apple Silicon and Intel Macs are both supported. Windows is planned.

Context in. Fix out.