Quey is available on desktop
The all-in-one platform for modern product teams. Design, iterate, and ship.
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.
Side by side
| Feature | Quey | Framer |
|---|---|---|
| What it is | Chrome extension for visual capture and agent handoff | No-code website builder with visual design and AI site generation |
| Where it runs | Any webpage, via a browser extension | Framer's own hosted canvas and CMS |
| Works on your own codebase | Yes — inspects and edits whatever your app renders in the browser | No — sites are built and published inside Framer's platform |
| Hands context to your coding agent | Yes — MCP bridge and structured clipboard payload | No — Framer's AI tools generate and edit Framer's own site internally |
| Design values captured | Colors, fonts, radius, spacing, and layout from the live element | Whatever is set inside Framer's canvas |
| Where your code lives | Your own repository, unchanged | Hosted on Framer's platform |
| Visual style editing | Yes — Frame/Font/Color tools with a live preview on the real page | Yes, native to Framer's builder |
| Pricing | Free tier, then $5/month Pro or $35 one-time lifetime | Free tier, paid hosting plans — see framer.com/pricing |
When to use each
FAQ
Yes — Quey works on any page rendered in Chrome. It won't have source-file hints for Framer-hosted pages the way it does for your own repo, but element, style, and design capture still work.
No. Quey never hosts your app. It captures context from the browser and hands it to your coding agent — your code stays in your own repository the whole time.
No. Quey doesn't build sites from scratch or generate new pages. It's for making targeted changes to an interface that already exists, with the context an agent needs to do it correctly.
More comparisons
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.
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.
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.
Keep your own stack
Install Quey, select the live element, and let your agent make the change in your own repo.
Add to Chrome© 2026 Quey. Built for extension-first coding workflows.
