Quey is available on desktop

Local provider

Meet
CLI

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.

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.
Type a change and press Enter to run a demo
@card-precision

Why it matters

Built for the browser-to-agent handoff.

01

Project-aware

Run the provider from the repository you want your agent to edit.

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

FAQ

Common questions

How do I install the Quey CLI?

Run `npx @quey/cli bridge start` from the root of the project you want your agent to edit — no global install required.

Does the CLI need to stay running?

Yes, keep the provider running in a terminal while you select UI in the browser so captures reach your local agent workflow.

Is the CLI local-only?

Yes. It runs a local MCP bridge on your machine — no browser captures leave your device except to the agent you configure.

Local setup

Start Quey where your code lives.

Run the provider from your project, then select the UI that needs work.

Install extension
Quey

Quey captures live browser UI context for source-aware coding agent workflows.

© 2026 Quey. Built for extension-first coding workflows.