Not that blue. This blue.
You’re doing design QA on a build, against your own Figma. It’s 90% right, and the last 10% takes four rounds of screenshots with red arrows. Deiko lets you point at the build and the Figma frame, say every fault once, and hand your developer or coding agent one brief where each screenshot comes with the name of the thing it shows.
Sound familiar?
The handoff was clear. The redlines were linked in the ticket. And yet, here you are again with the screenshot tool open.
- You write “move it 4px left.” Three messages later: which 4px, which direction, left of what.
- Another screenshot, another red arrow, each one a reply to the last. The caption now says “no, the OTHER card.”
- The button in the build is a perfectly nice blue. It is not the brand blue. You pull up the token doc and screenshot the hex. Again.
- You open the build and every icon you drew has been swapped for a library set nobody asked for. The redlines were inspected. Then ignored.
Here’s the same moment with Deiko
One pass over the screen, out loud, with both windows open. Then one message, not four.
-
Point at the build and the Figma. Say it once, all of it.
Double-tap ⌥ Right Option and a red bar tells you Deiko is listening. Rest the cursor on the build’s card, then on your Figma frame; each rest takes a crop of what’s under it. To circle something, hold ⌥ Left Option and draw. Tap ⌥ Right Option to stop.
“This card. Sixteen, not twelve. This blue is the header blue, use that one. And these icons are ours, not the library’s.”
Illustration: your Figma frame beside the build, a pin on each, the icon row circled. -
Every crop arrives with the name of the thing it is
Deiko turns it into a brief: what you said, cleaned up, and a screenshot of everything you pointed at, in the order you pointed. Each crop carries the element’s name, the window it came from, the text on screen and the words you said over it. So nobody changes the wrong component.
Pick a persona: Code change for the agent, QA ticket for the board.
Illustration: what the agent gets, crop by crop, each with its name and your words. -
Drop it wherever the fix is being made
A coin appears. Drag or flick it onto any window with a text box, and Deiko pastes the brief and presses Return. Claude Code and Cursor get file paths to the screenshots; ChatGPT or Claude.ai in the browser get the images attached. Nothing to install on their side.
Handing it to a developer instead? The QA ticket persona can ask the agent to file it in Jira, Linear or GitHub when it has those tools, or write it out in full for that tracker.
Illustration: the coin, ready to throw. The last line says which task it carries on from.
Round two already knows round one
Every brief is filed with the task it continues. When a coding agent finishes, it writes back what it did, and that shows under the brief as What came back.
So on Friday, when you point at the checkout card and say “same treatment as the pricing one”, the brief carries Tuesday’s decision: header blue, 16 padding. Nobody scrolls back through a thread to find it. If Deiko can’t tell which task a brief belongs to, the card asks “Which one?”
when you don’t need this
One nudge, one screenshot, one sentence? Paste the screenshot. It’s quicker, and it’s free.
Deiko is for the pass where you spot five things across two windows, and want round two to know what round one decided.
Your unreleased work stays yours
- It records when you say soA red bar sits at the top of every screen while it records, and can’t be hidden while the mic is on.
- Screenshots stay on your MacThey leave inside a brief you throw at an agent yourself, and no other way. The recording is deleted as soon as the brief is made.
- No accountNo email, no password, no profile. A screenshot showing a password or key is held back and deleted.
Questions designers ask
Can I point at my Figma frame and the build in the same brief?
Yes. Deiko sees whatever is on your screen, so rest the cursor on the build’s card, then on the Figma frame, in any window or on either monitor. Every crop lands in the brief in the order you pointed, with the words you said over it.
How does the agent know which element I meant?
Each crop arrives with the name the app gives that element (its accessibility label, like button “Select this plan”), the title of the window it came from, the text on screen, and what you said while pointing at it. Hold Left Option and draw to circle a region instead, like an icon row.
Does it work with Claude Code, Cursor and ChatGPT?
It works with anything that has a text box: Claude Code, Cursor, Codex, Windsurf, ChatGPT and Claude.ai. Agents on your Mac get file paths to the screenshots; browser chats get the images attached. Nothing is installed on the agent’s side. If the fix goes to a developer instead, the QA ticket persona can ask the agent to file it in Jira, Linear, GitHub, Notion or Confluence when it has those tools.
Does Deiko connect to Figma?
No. It works from your screen, not your files: a crop of what you point at, plus that element’s name, window title and on-screen text. No plugin, no Figma access, and no account.
Will the next round remember what we decided?
Yes. Every brief is filed with the task it continues, and coding agents write back what they did. The next brief on that work carries what was tried and decided, like header blue, 16 padding. If Deiko can’t tell which task a brief belongs to, it asks.
Show, don’t type.
For macOS 14 or newer on Apple silicon.
Everything, Pro included, is free until 24 October 2026. After that, Pro is $7.99 a month, $79 a year or $159 once, and Deiko stays free to use with transcription on your Mac.