Core Workflow
Move from rendered feedback to retained agent work without translating context by hand.
Field guide · 02
Try Waypoint
Interactive demoOne button. One Annotation. See how feedback becomes a change.
Try one small change in a practice app. No extension or agent connection needed.
Workspace settings
A little room for your next idea.
- Workspace name
- Weekend project
- Notifications
- Weekly digest
Annotate the rendered interface
Start with a small, visible change. Choose Annotate in the Waypoint toolbar, then select the button, heading, or other element that needs attention. That selected element is the Annotation’s Target.
Write the outcome you want: “Change this button label to Save changes. Keep its current size and position.” Save the Annotation, then open the Queue to find it. You do not need Design Actions or Variants for an ordinary request.
Let the Queue retain the work
Saving creates a Pending Annotation in the local Queue. Watch can deliver that activity without Claiming or removing it. The record remains inspectable as an agent Claims and resolves the request.
Hand the request to your agent
Without MCP, select the work in the Queue, choose Copy, and paste it into your coding-agent chat. Ask the agent to implement the request in the project. Copying provides context; it does not itself change your source code or complete the work.
With MCP connected, ask the agent to read Waypoint for your app’s URL. Include the actual host and port, especially when you run more than one project. Ask it to implement the saved request and verify the result.
Read my Waypoint annotations for http://localhost:3000/ and implement the button-label request. Verify the change before resolving it.Resolve with evidence
In the MCP workflow, the agent Claims the Annotation before editing, implements the request, verifies it, and marks it Resolved. Open your app and check the result yourself. A Resolved status records completion; it does not replace your review.
Design Actions require a structured Resolution Record describing the result and verification. Ordinary Annotations resolve without that record. Resolved and Discarded Annotations remain history until explicit Deletion.
Preview an edit without changing source
For a single Target, Element Edits let you describe changes to text, styles, or CSS and preview them in the page. Use this to make your request concrete before handing it to the agent.
A browser preview is not a saved source-code change. The agent still needs to locate the implementation in your project and apply the change there. Verify the resulting app after implementation.