BROWSER CONTEXT FOR YOUR AI

The bug happened.
Let your AI
see it, too.

Record what went wrong in Chrome. Mark the frame. Give Claude Code the recording and console context through MCP.

No account to create. PRO is $29.99, one time.

localhost / your-app REC
Tasks4 totalFilter: re
Review PRdisappeared
Reply to invoice
1

I deleted the other task.
Why did this one disappear?

CONSOLE[list] remove(index=1)
visible=2 · total=4
Illustrative demo · one recording, more context
Made for the way developers debug.
Chrome extensionMCP serverYour AI assistant
01 / THE WORKFLOW

Less explaining.
More actual context.

A screenshot shows a moment. A recording gives your assistant the steps and console output around it.

  1. 01

    Record the problem

    Start recording, then reproduce the bug in Chrome. Capture the sequence instead of rebuilding it from memory.

  2. 02

    Point out what broke

    Open a recorded frame, draw around the problem, and add a note. The drawing says where. The note says what.

  3. 03

    Ask your AI to inspect it

    Use the MCP connection to give Claude Code access to the recording, frame annotations, and console context.

Inside ChromeDebug
ChromeDebug frame editor showing a red rectangle around a misaligned quantity column and a numbered note explaining the problem.

Numbered shapes and notes give the AI a precise reference on the frame.

Product screenshots use demo data. Free recordings display a watermark; PRO removes it.

02 / CAPTURE THE RIGHT CONTEXT

Not every bug
holds still.

Four recording modes, plus quick screenshots. All available in the free trial.

Workflow

Capture clicks and inputs as a sequence, with console logs and optional screenshots per action.

For bugs with a specific sequence

Screen

Capture frames at regular intervals with console output attached to the recording.

For watching a problem develop

Video

Record for playback, with cursor movement and clicks drawn over the frames.

For movement and timing

Screenshot

Click to capture, with an optional countdown to get a dropdown or tooltip into view.

For the moment that disappears
03 / GET CONNECTED

Your browser.
Your editor.
One connection.

Install the Chrome extension and companion server, then connect Claude Code. You’ll need Node.js 18 or later.

Full setup and troubleshooting
1

Add the Chrome extension

Start with 25 recordings across all four modes.

Add to Chrome
2

Install the MCP server

npm install -g @dynamicu/chromedebug-mcp
3

Connect Claude Code

claude mcp add chromedebug -s user -- chromedebug-mcp

Restart Claude Code after adding the server. Open the extension and check that it shows Connected.

AFTER YOUR FIRST RECORDING, ASK

“Look at the last ChromeDebug recording. What happened when it broke?”

04 / SIMPLE PRICING

Try the workflow.
Keep it for good.

One extension. Start free, then unlock PRO with a licence key. No subscription.

FREE TRIAL
$0

25 recordings to see it for yourself.

  • All four recording modes
  • Frame annotations and console context
  • Quick screenshots and clipboard copies
  • Watermarked images
Start free

25 total recordings, not a daily allowance.

CHROMEDEBUG PROPAY ONCE
$29.99one time

Keep recording. Keep the context.

  • Unlimited recordings
  • Everything in the free trial
  • No watermarks, including on trial recordings
  • MP4 video and ZIP exports
Get PRO

Secure checkout through Lemon Squeezy.

Already have a key? Open the extension → I have a licence key. PRO activates in your own Chrome profile; browser windows launched with a temporary profile stay on the free trial.

YOUR RECORDINGS STAY LOCAL

Browser context.
On your terms.

ChromeDebug stores recordings on your machine, in your browser or the local companion server. No ChromeDebug account. No recording uploads. No extension telemetry.

When your assistant reads a recording, the context it reads goes to your chosen AI provider. PRO activation may make a one-time licence validation request to Lemon Squeezy.

This homepage sets no analytics cookies. If you arrive from one of our campaigns, its campaign label can accompany your checkout so we can understand which campaigns lead to sales.

Read the privacy policy
A FEW DETAILS

Before you
hit record.

Do I need both the extension and the server?

To hand recordings to your AI through MCP, yes. Screen and Video recordings and quick capture can also work in browser-only mode. Workflow and Screenshot recording modes require the companion server.

What counts toward the 25 free recordings?

The free trial is a one-time allowance of 25 recordings, shared across browsers signed into your Google account. A quick screenshot also counts as one capture. It does not reset each day.

What does my AI receive?

Your assistant can use the MCP tools to retrieve recorded frames, available interaction and console context, and the numbered notes you attach to annotations. Your chosen AI provider processes the context your assistant reads.

Is PRO a subscription?

No. PRO is a $29.99 one-time purchase. Paste the licence key into the extension you already have to unlock unlimited recordings, watermark removal, and MP4 and ZIP exports.

Will PRO work in an AI-launched Chrome window?

PRO belongs to your own Chrome profile. A window launched by the MCP server with a temporary profile remains on the free trial. Connect your assistant to your existing Chrome profile to use your PRO licence there.

Where can I get help?

See the setup and troubleshooting guide, or email support@dynamicupgrade.com.

THE NEXT TIME IT BREAKS

Show what happened.

Start with 25 free recordings