Security

Loopback by default

The Waypoint server binds to IPv4 loopback by default. Annotation data and local JSON persistence remain on the developer machine, and the website never attempts to discover or connect to a visitor’s local server.

Decide what context to share

An Annotation can include your comment, page URL, selected element text and context, captured styles, and optional screenshots or attachments. Review the page and request for sensitive information before sharing them with a coding agent.

Use the screenshot setting to control capture, and grant site access only where you want to annotate. Copied feedback goes wherever you paste it. MCP makes context available to your connected agent, whose provider and data policies still apply; local storage does not mean the agent processes everything locally.

Find and remove retained data

The extension keeps browser-side data, and the local server persists Annotation records in ~/.logbook-waypoint/annotations.json. Stopping the server does not erase those records.

Use Settings → Data & Storage to inspect projects and permanently remove stored Annotations. Review unfinished Variant work before deletion so your agent can clean up any temporary source code. Removing the browser extension or CLI is a separate operation from managing retained server data.

Narrow browser boundary

Waypoint exposes no public page-world Annotation CRUD bridge. A narrow read-only probe may assist React Source Identity, but Source Identity is untrusted context rather than guaranteed source mapping.

Host validation, bounded payloads, explicit site permission, and local-only defaults are part of the active boundary rather than optional deployment advice.