Install the guide, keep its map current from CI, tune it without deploys, and integrate with the API.
Install Wayfind code mode in a Next.js App Router project, with the setup wizard or by hand.
Install code mode in Vite single-page apps and in Electron or Tauri renderers, including screen capture for vision.
Script mode reference. Covers tag attributes, how controls are learned, the CSP directives you need, single-page apps, and what lite mode can't do.
Build the map on every build, commit it for rename aliases, upload it from CI, and comment map changes on pull requests.
The code-to-UI map (IDs, render conditions, reveal chains, status text, risk) and how the guide stays grounded in it.
What the guide may and may not do, how prompt injection is contained, and the setup agent's enforced boundaries.
Voice providers, latency expectations, screen capture modes, privacy, and how long sessions stay up.
Tell the guide the user's role, plan and feature flags with getContext, so it can explain UI the user can't see.
Projects, publishable and secret keys, live and test modes, allowed origins, and key rotation.
Change risk classes, labels, visibility, sensitivity and notes from the dashboard without a deploy.
What the analytics dashboard measures, where each metric comes from, and the privacy settings.
Plans, quotas, what happens at the limit, team roles, and enterprise options.
Reference for wayfind.config.json, runtime props and script attributes, build plugin options, and every environment variable.
Reference for wayfind index, wayfind diff, wayfind upload and npx wayfind-setup.
The hosted Wayfind API. Covers authentication, endpoints with request and response examples, rate limits, and errors.
Reference for the analytics events the runtime emits, how sessions are defined, and the tool failure reasons.
Reading a page needs a free account — create one or sign in.