← All use cases

Build an AI tour guide

Teach users your app through a guided walkthrough that adjusts to them as they progress.

Ask ZeroTwo to put a WebMCP-driven tour into your web app. It points at the next control, says what to do, and adjusts to where the user is while they do the steps themselves.

Advanced
Long-running

Best for

  • New users finishing a first workflow in a web app.
  • Onboarding that varies with app state.

Starter prompt

I want a guided tour inside our web app that walks a first-time user through creating their first project. Read the UI code and the docs folder, then expose tools the tour agent can call to list highlightable controls, read the current screen state, wait for the user to act, and show the next hint. Keep those tools separate from anything that changes data, so the user does every click themselves. Verify it in a browser starting from a signed-out state, and don't deploy.

Introduction

WebMCP tools that expose your app's controls, state, and docs let an agent choose each next instruction from what the user actually sees, while the user does the clicking. ZeroTwo writes the tools in your repo; in the desktop app, its built-in browser can discover and call them when you test the page.

How to use

  1. Open the repo in a Work task (or Code, where available) and choose one workflow.
  2. Supply docs and the starting states to handle.
  3. Run the starter prompt to add targets, state tools, and instructions.
  4. Test in the desktop app's built-in browser. Under Settings > Browser, Enable site tools lets ZeroTwo discover and call the tools a page registers through WebMCP.

Verify one narrow tour end to end before adding others.

Example: Add a Google Drive folder

Suppose a new user asks the tour for help with this request.

Walk me through adding a Google Drive folder.

Connect Google Drive

If Drive is not connected, the tour highlights the Connect Google Drive control and explains how to start.

Open the file explorer

Once connected, the next step follows the new state.

Add the folder

After the toolbar expands, the tour highlights the add-folder control.

Give the agent the context to guide users

Three contexts are needed: targets, state, and docs. The tool names below are suggestions; adapt the roles to your app.

Make controls discoverable

Give targets stable data-tour-id values with labels and descriptions, exposed through tools such as listTargets, showTourStep, and dismiss.

Read state and wait for the user

A getUiSnapshot tool can report state such as sign-in, and a tool like waitForUiChange(...) can wait for the user. Progress should depend on app state, not on instructions already shown.

Keep instructions with the app

Bundle Markdown docs with the app and serve them through tools such as readInstructionsForAIAgents, listDocumentation(), and getDocumentation({ name }); no separate plugin is needed.

Review the tour

Test varied starting states, canceled steps, and hidden controls; the agent should never claim success merely because it highlighted a button. Leave auth and permissions in the existing flow.

Good follow-ups

  • Test with Drive connected and the explorer closed.
  • Handle cancel then resume.
  • Add the next workflow.

Related use cases