Reach for Quey when
- You don't want to add another widget to your app's bundle
- You want to make the style change yourself and hand off the result, not just describe it
- You want the same extension to work across every project you open in the browser
localhost:3000
Now in public beta
Build faster,
ship with confidence.
The all-in-one platform for modern product teams. Design, iterate, and ship.
2.4×
faster iteration
98%
user satisfaction
10k+
teams onboarded
⚡
Lightning Fast
Deploy in seconds with one-click builds and zero downtime.
🎯
Precision Tools
Edit exactly what you mean, nothing more, nothing less.
🔒
Secure by Default
Enterprise-grade security and compliance out of the box.
Quey vs Agentation
Quey vs Agentation: annotating feedback vs editing the UI directly.
Agentation is an overlay widget embedded in your app for leaving pixel-precise feedback notes that an agent can read and act on. Quey takes a more direct path: select the element, edit the actual style live in the browser if you want to, and hand the agent a structured capture — as a browser extension, with nothing added to your app.
Side by side
Quey vs Agentation, feature by feature.
| Feature | Quey | Agentation |
|---|---|---|
| What it is | Chrome extension for visual capture and agent handoff | Overlay widget for annotating UI and leaving feedback for AI agents |
| Where it runs | Any webpage, via a browser extension — no app changes | Embedded in your app as an overlay widget |
| Works without adding anything to your app | Yes | No — added to your app as a widget |
| Hands context to your coding agent | Yes — MCP bridge and structured clipboard payload | Yes — MCP integration with two-way agent conversation |
| Visual style editing | Yes — Frame/Font/Color tools with a live preview on the real page | No — annotation and feedback threads, not live style edits |
| Annotation / comment threads | Yes — pin-based comments with resolve state | Yes — this is its core workflow, including two-way agent replies |
| Freezing CSS/JS animations to annotate a frame | Not currently supported | Yes — a stated feature |
| Pricing | Free tier, then $5/month Pro or $35 one-time lifetime | See agentation's pricing page |
When to use each
Neither tool is wrong — they fit different moments.
Reach for Agentation when
- You want a persistent, in-app feedback thread that other teammates can also use
- You need to annotate a specific animation frame that's hard to catch live
- You prefer a conversational, two-way loop with the agent over a one-shot capture
FAQ
Common questions
Does Quey support live two-way conversation with the agent like Agentation?
Quey's Agent panel lets you write an instruction alongside the capture and stream the agent's response in the toolbar, but its core workflow is capture-then-handoff rather than an ongoing annotation thread.
Do I need to add Quey to my app's codebase?
No. Quey runs as a Chrome extension with nothing added to your app. The optional local MCP bridge runs as a separate CLI process in your project directory, not as an in-app widget.
Can Quey annotate a paused animation frame?
Not currently. Quey captures whatever is rendered at the moment you select an element; it doesn't have a dedicated animation-pausing tool.
More comparisons
See how Quey compares to other tools.
Quey vs Figma
Figma is where teams design UI before it's built. Quey is for after it's built — selecting the real, rendered element in your live app and handing an agent exactly what changed and where. They solve different problems and most teams that use Quey still design in Figma first.
Quey vs Framer
Framer is a website builder — you design, publish, and host inside Framer's platform. Quey is a browser extension that works on any site, including apps that live entirely in your own repo, and its job ends the moment your coding agent has the context it needs to make the edit.
Quey vs React Grab
React Grab and Quey solve a similar problem — turning a clicked UI element into context a coding agent can act on. The main difference is where they run: React Grab is installed as a dependency inside your React app, while Quey is a Chrome extension that works on any page without touching your codebase, plus adds visual style editing on top of capture.
Capture, edit, hand off
Go straight from selection to a real style edit.
Install Quey and select the live element — no widget to add, no app changes required.
Add to Chrome
© 2026 Quey. Built for extension-first coding workflows.