FIX WHAT IS BROKEN

Turn a console error into a fix

Pasting a stack trace into a chat loses the two things that made it solvable: what was on screen when it fired, and what you were doing at the time. A recording keeps all three together, so the agent is not reasoning about an error in isolation.

Quick answer

To turn a console error into a fix, record the run that produces it with the console open, and say what you were trying to do. Paste the Clipy link into an AI agent like Claude Code, Codex or Cursor. It reads the error next to the screen state behind it, plus console and network diagnostics when the capture collected them.

Product walkthrough. Tap for sound.

What to record

  1. Open the console before you start, so the error is visible as it appears.

  2. Do the action that triggers it.

  3. Let the console output sit on screen long enough to be legible.

  4. Say what you were trying to do when it fired.

Say this while you record

Name the user-facing symptom as well as the error. The error is what the machine saw, the symptom is what you actually want fixed.

The prompt to paste

Replace the link with your own recording's share URL, then paste this into Claude Code, Cursor, Codex, or whichever agent you connected.

Read https://clipy.online/video/<id>

It is a recording of an error happening in this app. Give me the error as precisely as the recording supports, what I was doing when it fired, and what was on screen at that moment.

Then trace it in this repo: which call produces it, why it is reachable from what I did, and what the fix is. If the recording's diagnostics are incomplete, tell me exactly what you would need me to re-record.

The last sentence matters. An agent that says "re-record with the network tab open" has saved you a whole cycle.

What the agent gets from that link

  • A summary of what happened

    A short written account of the recording, so the agent starts with the shape of the request rather than a wall of raw text.

  • A timestamped transcript

    Your narration with times against it, when audio was captured and processed. This is where your reasoning lives, and it is usually the part that decides whether the agent fixes the right thing.

  • Key moments with frames

    Selected instants from the recording with an image of the screen at that point, so the agent can look at the state you were describing instead of guessing at it.

  • Browser diagnostics

    Console output and network activity collected during the run, for captures that collect them. This is what turns a red screen into an actual error string the agent can search for.

What changes

Writing it downRecording it instead
What the agent receivesThe part of the stack trace that fitted in your clipboard.The error, the screen behind it, and what you were doing.
Reproduction stepsWritten separately, usually after the fact.Already in the recording.
Follow-up questions"What were you doing when this happened?"Already answered.

Tips

  • Connect your agent once

    Run the setup at /agent-setup once. After that every Clipy share link works in the same session you are already in.

  • Use bug capture for structured diagnostics

    Chrome extension tab recordings with Capture bug context on collect console and network data as structured diagnostics. A plain screen recording of a console also shows the text in the frames, which is often enough.

  • A console at default zoom may not be legible in a frame

    If the error text is tiny it is tiny in the frame too. Bump the console font size, or read the error out loud, which puts it in the transcript as text.

  • Paste the link once the transcript shows

    The transcript, summary and key moments appear on the watch page moments after Stop.

Common questions

Do I still need to paste the error text?

Usually not, if the console is legible in the recording or you read it out. Pasting it as well does no harm and costs nothing.

Will the agent see network requests?

For captures that collect browser diagnostics, yes. For an ordinary screen capture, it sees whatever is visible in the frames, which means opening the network tab on screen works as a fallback.

Does this work for server errors?

If the error is visible on your screen, in a terminal or a log viewer, then yes, the same way. The recording does not reach into your server on its own.

Other jobs

The same job, elsewhere on Clipy

This page is the job. These cover the same ground for a specific agent, a specific team, or as a tool you can open right now.

The full list is on the use-case index. If your agent is not connected yet, start at agent setup.