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.
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.
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.

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.

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.

Queue up bug fixes from your couch
Real captures from real apps — a scribble and one line is all your agent needs.








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.
- APP-104Login button misaligned on iPhone SETo Do8 months
- APP-131Dark mode flashes white on launchBacklog6 months
- APP-167Weird bottom padding on AndroidTo Do5 months
- APP-198Scroll jank in settings listBacklog4 months
- APP-215Typo on the paywall screenTo Do3 months
- APP-233Empty state flashes before data loadsBacklog3 months
- APP-241Keyboard covers the notes fieldTo Do2 months
- APP-258Share sheet opens the wrong tabBacklog6 weeks
- APP-262Onboarding progress dots miscountTo Do5 weeks
Noticed a tiny glitch on Tuesday — gone in Thursday's update. Whoever builds this doesn't let anything slide.
Every update fixes the little things. This app feels loved.
No jank anywhere. You can tell someone sweats the details.
Giving feedback to your coding agent just got delightful
“If you told me this was a YC startup, I'd believe you.”
“Super seamless — I just had Claude set it up for me and produce the link.”
“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.”
“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.”
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.
- Everything in Pro, forever
- One payment — no renewals
- Direct line to the founder
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.



