01
Project-aware
Run the provider from the repository you want your agent to edit.
Quey is available on desktop
Local provider
The Quey CLI starts the local provider inside the repo you want to edit. Browser captures arrive already scoped to the right project, ready for your coding agent without any extra wiring.
The all-in-one platform for modern product teams. Design, iterate, and ship.
Why it matters
01
Run the provider from the repository you want your agent to edit.
02
Use one command during development instead of wiring a custom bridge.
03
Keep browser capture and source editing in your existing dev environment.
Workflow
Each product surface uses the same structure so visitors can compare capabilities without relearning the page.
Run
Launch the CLI in the project directory before selecting UI.
Capture
Quey sends the selected element context to the local session.
Edit
Hand off the payload to the tool already working in that repository.
Developer loop
One command connects the browser to your repository. Run the provider where your code lives, and every capture arrives already scoped to the project you want to edit.
Run from project root
Receive browser context
Pair with MCP
Use with coding agents
FAQ
Run `npx @quey/cli bridge start` from the root of the project you want your agent to edit — no global install required.
Yes, keep the provider running in a terminal while you select UI in the browser so captures reach your local agent workflow.
Yes. It runs a local MCP bridge on your machine — no browser captures leave your device except to the agent you configure.
Local setup
Run the provider from your project, then select the UI that needs work.
Install extension