Walkthroughs for Your AI Assistant
Part of the MountDev Ops Walkthroughs documentation. Updated November 13, 2026
MountDev Ops Walkthroughs documentation | Updated November 13, 2026
Your own AI assistant, connected in Settings, Connections, can read, write, and remove walkthroughs as plain words, with the same checks as the screens.
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 3,859 automated checks before it ships, and every screen change is walked through before release.
The Tools
Each tool is its own permission, so you choose which ones a connection gets, one at a time.
| Tool | Permission | Level | What it does |
|---|---|---|---|
walkthroughs_list | walkthroughs.list | Read | Lists the walkthroughs: name, kind, where each runs, who sees it, whether it is on, its version, and how many steps. It reads them a page at a time. |
walkthroughs_get | walkthroughs.get | Read | Shows one walkthrough by its number, with every step. |
walkthroughs_save | walkthroughs.save | Write | Adds a walkthrough, or changes one by its number. |
walkthroughs_delete | walkthroughs.delete | Delete | Removes one walkthrough for good, with its steps. |
The actions behind them are walkthroughs.list, walkthroughs.get, walkthroughs.save, and walkthroughs.delete. A connection only gets a tool you ticked for it, and only if the person who made the connection could do that themselves.
How to Write One
Send the walkthrough as data: name, kind (guided or hints), where ({ "type": "workspace", "page": "helpdesk" }), start ({ "on": "first_visit" }), audience (everyone, a permission, portal.client, demo.visitor, or website.visitor), and steps. Each step has a kind (card, highlight, welcome, beacon, or wait), a target (step, attr, role, words, css, page, and label), title, text, button, advance (next, click, popup, saved, or appear), shows (now, popup, or later), and delay_ms. Words are plain text only: HTML and code are refused.
What Stays with People
- Saved off. Everything your assistant saves is off and marked as saved by an AI assistant. Saving a change to a walkthrough that is on turns it off.
- Turning on is a person's. Only a person turns a walkthrough on or off (action
walkthroughs.state); there is no tool for it. - No tracking. Your assistant never sees who finished or skipped a walkthrough, and never records it for anyone.