Skip to main content
New: 189 SEO checks now available. See what's new
Chrome extension · Bug reports developers can act on

From “something's broken” to a task your coding agent can fix

Capture the page with its console errors, ask for a fix, and the developer finds it in their editor as a task with the screenshot attached — ready for Claude Code. When it is fixed, verify it from the same place.

From a report to a fix your coding agent can start on — with nothing lost in between.

  • Free to install
  • On the Chrome Web Store
  • Nothing is sent until you choose to

Hover to play

Sound familiar?

The problem

Bug reports arrive as a vague sentence and a cropped screenshot. The developer has to reproduce it before they can even start.

Reports arrive without the details

Which page, which browser, which error — the developer has to reproduce it first.

The report and the code live in different places

Copying a ticket into the editor is where context and screenshots get dropped.

Nobody knows if it was fixed

The reporter never hears back, and the bug quietly returns.

What changes

Before and after Dr Urls — Capture

Without it
With Dr Urls — Capture
A sentence and a cropped screenshot
A full capture with console errors and the environment attached
Copy-paste from the tracker into the editor
The task appears in the repo's .drurls folder, screenshot beside it
The developer reproduces the bug before starting
“Fix this capture” hands it to Claude Code with everything in it
“Fixed?” asked in chat, weeks later
One status from reported to fixed to verified, seen by everyone

How it works

4 steps, start to finish

  1. 1

    Capture it

    Screenshot or record the page. The console errors, viewport and timings are attached automatically.

  2. 2

    Ask for a fix

    Press “Ask to fix” on the capture, in the side panel or on the dashboard.

  3. 3

    It lands in the editor

    Dr Urls Sync writes it into the developer's .drurls folder as a task with the screenshot, the console output and your notes.

  4. 4

    Fix, then verify

    “Fix this capture” hands it to Claude Code. Once fixed, it is marked fixed — and someone confirms it with a new capture.

What you get

  • Reports that already contain the console errors and the environment
  • One status from report to fix to verification, visible to the whole team
  • A file a coding agent can read, with the image beside it

Who it's for

  • Reporters

    Capture what you see; the technical detail is collected for you.

  • Developers

    Start from a task file with the evidence, not a vague ticket.

  • Team leads

    See every report's status without chasing anyone.

No surprises

Good to know

What it does not do, said up front.

  • The developer side needs Dr Urls Sync in VS Code, Cursor, Windsurf or VSCodium.
  • The fix is written by the developer or their agent; Dr Urls carries the report and tracks the state, it does not change your code itself.

FAQ

Questions

Does the reporter need to be technical?

No. They capture what they see; the technical detail is collected for them.

Can it go to GitHub instead?

Yes. Dr Urls Sync can send tasks to GitHub issues.

From a report to a fix your coding agent can start on — with nothing lost in between.

Free to install. Your work goes to a free Dr Urls account, filed against the site it is about.

  • Free to install
  • On the Chrome Web Store
  • Nothing is sent until you choose to