Spot a bug. Point at it. Your agent fixes it.

Press one key, click the broken part, say what you expected. Darnly hands Claude Code, Codex or Cursor everything it needs to fix it on the first try.

Add to ChromeGet the Mac app
Works withClaude CodeCodexCursor
How it works

No screenshots to drag. No explaining twice.

Today a bug costs you a screenshot, an app switch, a hunt for the right file and a paragraph of description. With Darnly it is three moves, and you never leave the page.

Step 1

Press the key

⌥ ⇧ B on any page, on localhost or your live site.

Step 2

Click the broken part

A red box follows your cursor. Arrow keys make it bigger or smaller. Esc cancels.

Step 3

Say what you expected

One sentence, then Enter. Got a picture of how it should look? Paste it in too. Then tell your agent "fix my bugs".

What your agent gets

The context a screenshot can't carry.

  • A screenshot with the element boxed in red and your note written on it.
  • The exact file and component that drew it, on your local project.
  • The element's selector, text, HTML and styles.
  • Console errors and failed requests from the last 60 seconds.
  • Clear rules: fix it, say what changed, ask if the note is vague.
.darnly/inbox/2026-11-01-0940-save-plan.mdmarkdown
# Bug on /plan: PlanBar

**Expected:** Save plan should be clickable
and save my week

## Element (the red box)
- selector: `button[data-testid="save-plan"]`
- code: `src/components/PlanBar.tsx:18` (start here)
- drawn by: `PlanPage` > `PlanBar`
- styles: opacity: 0.45; pointer-events: none

## Errors (last 60s)
- console.error: Save failed: plan is undefined

## Failed requests (last 60s)
- POST /api/plan?token=[hidden] 500 (41 ms)
Darnly for Mac

Bugs outside the browser, too.

A small menu bar app for Mac apps, the iOS Simulator and the Android Emulator. Same three moves, same inbox, so your agent already knows what to do.

  • Press ⌥ ⇧ D anywhere, click the broken part, type what you expected.
  • The element comes from macOS accessibility: its kind, label and accessibility id (testID in React Native), the best clue to the code.
  • Errors from the last 60 seconds: the Simulator, the Emulator (adb) or the Mac app's own log, secrets hidden.
  • Works on menu bar and notch apps. A welcome screen sets up the folder and permissions on first launch.

Early access: write to hello@darnly.dev for the Mac download.

.darnly/inbox/2026-11-01-0805-popup-gradient.mdmarkdown
# Bug in Maccy: group "Clipboard history"

**Expected:** Popup background should use the
brand gradient

**What it should look like:** .reference.png
(a picture you pasted into the note)

## Element (the red box)
- kind: group (`AXGroup`)
- accessibility id: `historyList` (start here)
- size: 450x312 at (0, 52) in the window

## Errors (last 60s)
No errors in the app's log in the last 60 seconds.
Private by default

Your bugs never leave your computer.

No account needed
Reports are files in your project, or text you choose to paste. Nothing is sent to us unless you switch on the optional cloud inbox for agents that can't see your files.
Secrets hidden automatically
Passwords, card numbers, tokens, API keys and cookies become [hidden] before anything is saved.
You choose the sites
Errors are recorded on localhost. Live sites only when you switch them on, one at a time.
darn·ly

"Darn it" is what you say when you spot the bug. Darning is how you mend the hole. Darnly sits between the two.

Live on the Chrome Web Store

Try it on your next bug.

Darnly is free and works in Chrome, Edge, Brave and Arc. Questions or feedback? Write to hello@darnly.dev.

Add to ChromeFollow @darnlyhq