Pincushion.

The loop, in 4 seconds.

Click anywhere on a live app, type what's wrong, and hit send. The agent reaches into the codebase and patches the layout in front of you. Pincushion does this against your local repo — point at a pixel, describe the fix, and the change shows up as a diff you can approve.

The path is short and legible: Chrome extension → MCP → VS Code → diff. A pin and a note become a patch, scoped to the exact element and the exact line.

Vibe-coding broke the feedback loop.

When you're prompting an agent to write a feature, the bottleneck isn't the code — it's describing what's wrong with the output. Designers and PMs end up screenshotting, annotating, pasting back, hoping the agent finds the right component.

Before Pincushion

Take screenshot → open Figma → annotate → copy-paste → "the button on the third card under the header." Minutes per pin, ambiguous, and stale within seconds.

With Pincushion

Click → type → send. The agent knows which element, which file, which line. Seconds per pin, unambiguous, and sourced to the line of code.

One feedback report, four surfaces.

The hard problem isn't the UI — it's threading a pixel-level report through the agent's tool layer and back into a code change the user can approve. Pincushion sits between the browser, the model, and the editor.

Three calls that shaped everything.

Every product has a small set of moves that decide what it is. Here are mine.

01 · Pin, not screenshot.

Screenshots are dead the moment the layout changes. A pin is a live anchor — when the dev re-renders, the pin re-attaches to the same element via a stable DOM signature. Same conversation, fresh state.

02 · MCP, not API.

Building one API client per agent (Claude, Cursor, Windsurf, etc.) is a quarter of work and a permanent maintenance tax. Going through MCP means anyone with an MCP-aware agent can read Pincushion reports for free — including agents that don't exist yet.

03 · Approve in the editor, not the browser.

It's tempting to apply the patch and have the user accept it visually. But the diff is the contract. Showing it in VS Code keeps the developer's mental model intact and lets them edit the agent's work before accepting.

Shipped surfaces.

Pincushion is in early access — built solo and live in market. The honest version of the outcomes page: what shipped, where it ships, what's next.

What's next · Q3

• Mobile-screen pinning (React Native preview).
• Pin → Loom-style replay for async review.
• Team mode: pin assignments + state machine.

What I'd do differently

Shipped the Chrome extension before the MCP server was solid. Got most of the experience working, but the integration story was confusing for two months. Next time, the protocol layer ships first.