Feedback on your live app. Fixed by your coding agent.
Share a live critique with clients, teammates, or designers. They pin exact UI issues with no extension or paid seat, and each pin reaches your coding agent with the screenshot, selector, and thread.
Connect my coding agent →No card · no reviewer accounts · no browser extension required
Need to pin any webpage? Add the Chrome extension →
Four steps.
Zero friction.
Anyone drops a pin
Your reviewer — client, teammate, designer friend — clicks any element on your live app and types a note. No account, no paid seat, nothing to install. We capture the selector and screenshot behind the scenes.
Discuss in place
Threaded comments appear right on the page. Context stays where it belongs — not in a Slack thread from last Tuesday.
Your agent picks it up
The pin arrives via MCP in Cursor, Claude Code, Codex, or Windsurf — selector, screenshot, viewport, thread, and project context in one call. No translating screenshots into prompts.
The loop closes
Resolving records the commit, branch, and PR. The deploy hook links the live deploy, and Pincushion AI re-checks the fix on the deployed site — so your reviewer sees their note shipped and verified, not just "marked resolved."
Also works for native iOS apps: generate a mobile crit wall from simulator screens and reviewers comment in a browser. Or skip the browser entirely — a note or screenshot emailed to your project's pin+…@in.pincushion.io address becomes a pin.
The feedback loop,
finally closed.
Agent slash commands
Type /pins, /my-pins, or /resolve in any supported IDE and your agent instantly pulls the relevant feedback and acts on it. Works in Claude Code, Cursor, VS Code, Windsurf, and Antigravity — zero extra config.
MCP agent integration
One command: npx pincushion-mcp. Your AI reads pins, claims them, writes the change, and resolves — all via Model Context Protocol.
Pincushion AI
AI feedback on every plan. Run /critique and Pincushion AI drops UI/copy/a11y pins on your page. Mention @pincushion in any thread for a follow-up. Workspace critiques use your connected agent and its model provider. Hosted Crit sends selected rendered-page evidence to OpenAI for analysis. Resulting feedback syncs to Pincushion.
Mobile crit walls
Turn iOS simulator screens into a browser-based critique wall with semantic hotspots. Reviewers comment without installing anything; your agent still gets source hints, screen context, and a repeatable mobile-wall publish refresh path after changes land.
Roles & permissions
Owners, developers, and commenters — each with exactly the right level of access. Commenters are always free. You only pay for developers.
An agent work packet, not a feedback item
Other tools hand feedback to developers. Pincushion hands it to your coding agent — selector, DOM snippet, screenshot, viewport, thread, project context, and acceptance criteria, all in one MCP call. Resolved pins keep the commit SHA, branch, and PR URL attached to the implementation record.
Slack & Teams notifications
Pipe pin activity into the channels your team already lives in. Subscribe to ready-for-dev pins, @-mentions, and follow-up replies — or opt in to every new pin and resolved change. Per-page filters, named subscriptions, one-click OAuth install.
Share a report, no install
Share a report at pincushion.io/r/<token>. It's a live screenshot of the page with real pin markers, threads, and status. Anyone with a public link can view it. Visitors can add pins and replies without an account only on projects open to feedback, after entering a name and email. Restricted feedback and viewing private reports require authorized sign-in. No extension is needed. Click into a resolved pin to see what the page looked like before, the PR that fixed it, and when it shipped.
Chrome & every MCP editor
Chrome extension for stakeholders who want it installed, or send a share-report link if they'd rather not. MCP integration + a VS Code/Cursor extension for Cursor, Claude Code, VS Code, Windsurf, and Antigravity. Real-time cloud sync keeps everyone on the same page. Works on production, localhost, staging, if it renders in a browser, you can pin it.
Plays nice with
your stack.
No agent required to file a pin — turn a support email, form, or monitoring alert into one. See the automation guide (REST API, n8n node, Zapier). Designers: see your live-app pins inside Figma.
Your agent doesn't
just read feedback.
Pincushion exposes an MCP server your supported coding agent can connect to. Approve a finding, then ask the agent to read the pin, make the change, and record the result. Unattended dispatch requires a separately configured agent loop.
Get Started// Connect in one command npx pincushion-mcp --project-dir . // Agent fetches open feedback get_feedback_summary() { "pins": [{ "selector": ".hero > h1", "comment": "Change to Welcome Home" }] } // Agent writes the change & resolves fix_and_resolve("pin_1", "Updated heading text") // done
See it on your own page first.
Not ready to wire up your agent? Drop your web URL and Pincushion AI pins concrete UI, copy, and a11y fixes right on your live page. Shipping native mobile? Generate a crit wall from simulator screens and use the same pin-to-agent loop. Keep the pins with a free account and invite your team — nothing to install on anyone's end.
Get my free crit →Free account, no credit card. Takes ~2 minutes.
Connect your agent.
Start in your repo with npx pincushion-mcp setup. Setup signs in, binds your project URL and prepares the client you explicitly choose. With Node/npm, a supported client runtime and model access available, it continues into a real critique and verifies the saved report before opening its link. Normal workspace/MCP trust, cloud-upload and report-visibility prompts still apply; private reports may require browser sign-in. Missing access leaves the run incomplete. Manual configuration below alone creates no report. If this came from a Crit report, use npx pincushion-mcp claim <report-token> to resume after authenticated project access is confirmed. The Chrome extension is optional for adding new browser pins.
VS Code & Cursor extension
VSIX installThe VSIX adds @pincushion as a Copilot Chat participant. Run the setup wizard separately to sign in, register the project, and choose an editor; restart the editor and read a real pin before treating the agent as connected.
After downloading, run code --install-extension pincushion-feedback-0.2.0.vsix (or drag the file into Extensions → Install from VSIX…). Marketplace listing also pending — VSIX is the canonical install for now.
@pincushion /pins — show all open feedback@pincushion /my-pins @you — your @mentioned pins@pincushion /resolve <id> — claim & close a pin@pincushion /feedback-summary — project overview@pincushion /implement — run the full approved-pin loop
Plus deploy-time AI critique via the deploy webhook — runs /critique on every push and auto-resolves landed pins.
Cursor
1-clickChoose Cursor in the setup wizard, or add the MCP server with this explicit one-click action.
Add Pincushion MCP to Cursor Cursor Marketplace — coming soonOr add manually to the project-local .cursor/mcp.json:
Claude Code
1 commandRun this once in your project root. Claude Code registers pincushion as an MCP server automatically.
Restart Claude Code, then ask it to call get_actionable_pins. Review an existing AI or human finding, approve that exact pin, and then ask it to implement the change.
Claude Desktop
Config fileAdd to claude_desktop_config.json. On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Replace /absolute/path/to/project with your repo path. Restart Claude Desktop after saving.
Windsurf
Config fileChoose Manual in the setup wizard, then open Windsurf → Preferences → MCP, or edit ~/.windsurf/mcp.json directly. The wizard leaves unsupported editor configs unchanged.
Antigravity
Config fileChoose Manual in the setup wizard, then add this to your Antigravity MCP config file. Use . for the project dir if running from your repo root, or provide an absolute path.
Any MCP Client
npxAny editor or agent runtime with MCP support can connect using npx. Choose Manual in the wizard and follow that client’s MCP instructions; point --project-dir at your repo root.
Also works with:
+ Zed, Cline, Continue, Goose, Amp, Codex CLI, and any MCP client
Full setup instructions on desktop.
For the new era —
when the product is the design.
| Design-file comments | pincushion | |
|---|---|---|
| Where you comment | A static design file | The product you've actually shipped |
| What you comment on | Pixels in a frame | Real DOM elements — CSS selector, XPath, coords |
| Source of truth | The design file (drifts from production) | The code that's actually running |
| Who acts on the feedback | Designer hands off, developer rebuilds | Pin lands in your IDE as agent-ready implementation context |
| Loop closes when | Designer marks the comment resolved | The change ships — pin auto-resolves on deploy |
| Stakeholder cost | Paid seat, or heavily limited guest access | Always free — no seat, no cap, ever |
Design-file comments belong on the file. Pincushion belongs on the live thing — for teams whose design lives in the code.
Three concepts that make the loop close itself.
More than a screenshot.
Every pin carries the CSS selector, surrounding DOM snippet, viewport size, full comment thread, project context, and optional acceptance criteria — all in one MCP call. Your coding agent gets the same picture you do, without you translating anything into a prompt.
Proof the fix shipped.
When a deploy includes pins your agent resolved, Pincushion AI revisits the page and writes back a verdict — verified, regressed, or inconclusive — directly onto the pin. Stakeholders see proof. Pro & Team.
The metric that matters.
Feedback tools brag about how fast they collect bugs. Pincushion brags about how fast bugs close. Median pin-to-PR, with a 5-pin minimum so the number is never a lie. Pro & Team, for your projects.
Start free.
Scale when ready.
Stakeholders are always free: unlimited reviewers, no seats, nothing to install. You only pay to unlock more projects and Realtime. No hidden fees, cancel anytime.
Free
Stakeholders always free. Devs get the full agent-native workflow on one project.
- Unlimited stakeholder seats — free forever
- Unlimited manual pins, comments & the full MCP workflow
- 25 AI actions / month — agent dispatches, AI replies, AI critique pins & deploy verifications (manual work never counts)
- Agent work packets — pins carry selector, DOM, viewport, thread & project context
- Assign-to-agent — one MCP call dispatches the pin to your local agent loop
- Branch / PR URL recorded on resolved pins
- Implementation packets (pins grouped by page)
- Slack & Teams routing for ready pins & mentions
- 1 project · Cloud sync (30s polling) · Slash commands for all IDEs
Pro
For teams shipping with AI coding agents
- Unlimited AI actions — no monthly pool on dispatches, AI replies, critiques & verifications
- Realtime push to your coding agent — pin → IDE in under a second
- Auto-link deploy URL — every deploy writes the live URL back to its resolved pins
- Post-deploy verification — Pincushion AI verifies the fix and writes a verdict (
verified,regressed, orinconclusive) on the pin - Time-to-fix metrics for your projects — median + p25/p75 of pin-to-resolve, with a 5-pin minimum so it's never noise
- Access controls — open, domain-locked, or invite-only
- Unlimited projects
- Everything in Free (agent work packets, assign-to-agent, PR linkage, AI critic, Slack/Teams)
- Priority email support
Team
For teams with multiple developers
- White-label crit reports — your logo on client-facing reports
- 3 developer seats included
- Additional developer seats at $12/mo each
- Unlimited commenters — free forever
- Everything in Pro (Realtime, auto-link deploy, post-deploy verification, time-to-fix metrics, access controls)
- Role management (owner, editor, commenter)
- @mention routing between team members
- Priority support
Stop screenshotting your product into Slack.
Just pin it.
Visual comments, dropped on the live thing — and shipped by your agent.
Try it on my app — free