Visual Feedback
Pin comments directly on your live app preview to request precise changes without long written explanations.
Visual Feedback lets you give change requests to AgentQ by clicking directly on the part of your app you want to update. Instead of describing where an element is, you pin a comment on it and write a short instruction.
Why this matters
Writing change requests is the biggest friction point for most users. Explaining location and structure with words ("the button below the section after clicking A...") slows iteration and creates back-and-forth.
Visual Feedback removes that friction by replacing long descriptions with one action: pin the element, say what you want.
Where to find it
Visual Feedback lives inside AgentQ Chat.
At the bottom of the chat panel, there is a toggle with two options:
- Chat: default text input.
- Visual feedback: pin-and-comment mode against the live preview.
Switch to Visual feedback to start pinning comments.
How it works
- Open your project so the live preview shows next to AgentQ Chat.
- Toggle to Visual feedback in the chat panel.
- The preview shows the prompt: "Click anywhere on the preview to pin a comment."
- Click any element to pin a comment and write a short instruction.
- Add as many pinned comments as you need across screens.
- Click Apply comments to send all pinned comments to AgentQ as a single, structured update.
Each pinned comment captures:
- the exact location you clicked
- the element context
- your written instruction
Typical workflow
- Open your project and make sure the live preview is visible.
- Navigate the preview to the screen or state you want to change.
- Switch the chat input to Visual feedback.
- Click an element and write a focused instruction (for example: "make this button primary").
- Repeat for other elements or screens.
- Click Apply comments to review the list.
- Send the full set of comments to AgentQ in one go.
When to use Visual Feedback
- Adjusting layout, spacing, alignment, or visual hierarchy.
- Renaming labels, buttons, or section titles.
- Reporting UI bugs tied to a specific element or state.
- Requesting design refinements on specific screens.
- Giving feedback after sign-in or in a deeper workflow state.
Best practices
- Reach the exact screen and state first in the preview, then switch to Visual feedback.
- Keep each pinned comment focused on one change per element.
- Group related comments before clicking Apply comments to keep updates reviewable.
- Combine Visual Feedback with text instructions in Chat mode when behavior changes are also needed.
Common issues
- Comment pinned on the wrong element: re-click more precisely on the intended element.
- Wrong screen state (logged out, wrong filter): navigate first, then switch back to Visual feedback.
- Too many comments at once: split into smaller batches so updates stay easy to review and roll back.