Amp adds a website feedback widget that starts a coding thread
Amp now lets you steer the agent from the page itself: a small widget on your site turns clicked elements plus written instructions into a new thread in your project. Amp then makes the change, and you ship it from that thread like any other edit.
Key points
- The widget is enabled per project in settings and needs one script on the site
- It stays invisible until you open a page with `?amp` or have used it before on that site
- Click an element, write the instruction, and use New Comment for additional elements
- Send makes Amp open a new thread in the project; you ship the change like any other
- First use requires signing in with Amp and approving a consent screen
Amp has shipped a feedback widget you can turn on from your project settings. After adding one script to your site, opening any page with `?amp` appended reveals the annotation overlay; ordinary visitors see nothing. You click an element, type what you want changed, and use New Comment to leave notes on further elements before hitting Send.
The first time, you sign in with Amp and approve a consent screen, then click Start in Orb. Amp opens a new thread in your project carrying your comments, and Open Thread jumps you there to make the change. You review and ship it from the thread like any other edit. Once used, the widget stays visible on that site until you hide it.
Real-world use
- A design team flagging alignment bugs on a staging site by clicking the element instead of describing it in chat
- A marketing team adjusting copy and button placement on a SaaS landing page without touching the codebase
- A frontend developer turning small mobile-layout defects into an agent task without filing a separate issue
Why it matters
Visual feedback turns hard-to-describe UI fixes into a ready agent task, removing the step of writing an issue and re-explaining the context.