The screenshot tool that fixes bugs

See a bug in your app — on the couch, on the train — send it to Drafty. Your coding agent picks it up, ships the fix, and sends back proof.

Works withClaude CodeCodexCursorAntigravityGemini CLI
How it works

Close the feedback loop

1. Install the iPhone app

Grab it from the App Store. Then point your coding agent at drafty.im/connect.md — one line, and it installs the Claude Code plugin, signs you in, and makes your first canvas.

2. Screenshot the bug

Screenshot the issue on your iPhone and share it to Drafty. Circle what's wrong and write one line so there's no ambiguity.

3. Claude Code fixes it — and shows you the proof

The fix arrives as a PR, paired with a proof canvas of before/after screenshots. You see the work before you merge it.

Mark it up

Show your agent exactly what you mean

Circle what's wrong, write one line, and send. Your agent sees exactly what you saw — no ticket, no back-and-forth.

The Drafty Annotate screen on iPhone: a glp3 screenshot with a magenta loop around the compounds list and the note 'Show all compounds', ready to send.
Your agent picks it up

A queue your agent drains

Captures land in the queue the moment you send them. On watch, your agent claims each card as it arrives, reproduces the issue, starts the fix — then hands it back for your approval, with receipts.

Claude Code on iPhone watching the glp3 inbox: a new 'Show all compounds' capture lands and the agent claims it — reproducing, fixing the root cause, and coming back with proof.
Verify the work

Every fix comes back with proof

This one's real — an actual proof canvas from an actual fix, exactly as the agent sent it back: the before, the after, and the receipts. Scroll it.

drafty/Proof: My Stack share cardShare
A Drafty proof canvas showing a real fix — the My Stack share card before and after, with the agent's receipts.
Open the real canvas →
The iPhone app

Queue up bug fixes from your couch

Real captures from real apps — a scribble and one line is all your agent needs.

glp3 stack card in Drafty — a magenta loop around the SIZE and DOSES tabs, with the note: can we lead with the options, then the preview, then the action buttons?
Journeys trip timeline in Drafty — a circle around a tiny stay icon, with the note: icon too small not legible.
Recipes home grid in Drafty — an arrow at the filter chips, with the note: move active chips up front.
glp3 Reminders settings in Drafty — circles on the toggle pills, with the note: this on state for switches looks weird.
Journeys stay options in Drafty — a box around the Airbnb options list, with the note: 2-col cards might be more functional?
Recipes detail in Drafty — a circle on the allergen warning icon, with the note: choose a better icon for allergen warning.
Journeys settings in Drafty — a loop around the agent panel, with the note: hide admin panel from users.
Recipes search list in Drafty — a long arrow up the list, with the note: sort by most cooked recipes first.
Before / after

Small bugs add up. So do small fixes.

Every bug you spot either piles up in a tracker, quietly souring the experience — or gets fixed the week you saw it, and turns into reviews like these.

Before Drafty
Backlog46 open
  • APP-104Login button misaligned on iPhone SE8 months
  • APP-131Dark mode flashes white on launch6 months
  • APP-167Weird bottom padding on Android5 months
  • APP-198Scroll jank in settings list4 months
  • APP-215Typo on the paywall screen3 months
  • APP-233Empty state flashes before data loads3 months
  • APP-241Keyboard covers the notes field2 months
  • APP-258Share sheet opens the wrong tab6 weeks
  • APP-262Onboarding progress dots miscount5 weeks
+ 37 more, untouched
After Drafty
Ratings & Reviews4.9
2d ago
Fastest dev I've ever seen

Noticed a tiny glitch on Tuesday — gone in Thursday's update. Whoever builds this doesn't let anything slide.

solobuilder_fan
1w ago
It just keeps getting better

Every update fixes the little things. This app feels loved.

km_reviews
2w ago
Small app, huge polish

No jank anywhere. You can tell someone sweats the details.

8bitgardener
Early reviews

Giving feedback to your coding agent just got delightful

If you told me this was a YC startup, I'd believe you.
Alex N. · Clove · Kiki.club
Super seamless — I just had Claude set it up for me and produce the link.
Jun · ING · Dovetail
I comment on the exact element like I would in Figma, and Claude ships the redesign on the same link. I don't screenshot anything anymore.
Michele · Thinkmill · ReactConf · Keystone.js
Claude finished the feature, couldn't attach the proof screenshots to the GitHub PR, so it made a Drafty link and shared it. Nobody told it to do that.
John · makes Drafty
Pricing

Try the whole loop free for 7 days.

Capture a bug, annotate it, and watch your agent ship the fix back with proof — the whole loop, free to try for a week.

Founding member
Lifetime
$99one-time
Lifetime Pro. No renewals, ever.
Only 42 available at launch
  • Everything in Pro, forever
  • One payment — no renewals
  • Direct line to the founder
Become a founding member — $99
FAQ

Questions

If your question isn't answered below, and I'll get back to you.

How is this different from filing tickets?

A ticket stores the problem; this closes it. Your screenshot goes straight to the agent that fixes it, and comes back as a PR with before/after proof — no triage, no backlog, no re-explaining next sprint.

How does my agent find out a screenshot arrived?

It lands in a queue — your inbox board. When your agent is on watch, a new capture wakes the session and gets claimed right away. When nothing's watching, it just waits in the queue, and the next session drains it. Nothing to paste, nothing lost.

What stops it shipping a bad fix?

You do. The default is a PR you review, with a proof canvas of before/after screenshots attached. Nothing merges itself — and if the fix is wrong, comment on the proof and the agent takes another pass.

Does my code go to Drafty?

No. Your agent works in your repo, on your machine, with your permissions. Drafty stores the screenshots, comments, and proof canvases — private or invite-only per canvas.

Do I need Claude Code?

It's built Claude Code-first — point your agent at drafty.im/connect.md and it wires up the plugin and skills for you. Codex, Cursor, and Gemini CLI run through the same plugin.

Can testers who aren't me send feedback?

Yes. Share a canvas link — guests comment without creating an account, and invited reviewers annotate the exact element, Figma-style.

What does it cost?

The full loop — bugs coming back fixed with proof — is Pro: $192/yr early bird, or $20 month to month, with a 7-day free trial and no card. While they last, there's also a founding offer: $99 once for lifetime Pro, limited to 42.

In the age of AI, it's unacceptable to leave bugs unattended.

Your agent is sitting right there. Screenshot one bug tonight — it comes back as a PR with proof.