01
Project-aware
Run the provider from the repository you want your agent to edit.
Local provider
Connect browser context to your local project.
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.
Why it matters
Built for the browser-to-agent handoff.
02
Fast setup
Use one command during development instead of wiring a custom bridge.
03
Local-first
Keep browser capture and source editing in your existing dev environment.
Workflow
The same simple loop on every page.
Each product surface uses the same structure so visitors can compare capabilities without relearning the page.
01
Run
Start the provider
Launch the CLI in the project directory before selecting UI.
02
Capture
Select from the browser
Quey sends the selected element context to the local session.
03
Edit
Use your coding tool
Hand off the payload to the tool already working in that repository.
Developer loop
A small bridge between browser review and source edits.
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
Local setup
Start Quey where your code lives.
Run the provider from your project, then select the UI that needs work.
Install extension