Every feature ships with its guide.
Your coding agent records the new feature as it builds it. Snaplore adds the voiceover and publishes the guide, the help article and the agent skill.
Agent-made walkthroughs on the Pro and Team plans · early access
Three costs you already count.
When docs fall behind shipping, it shows up in your release checklist, your support queue and your help center. Each one has a fix in Snaplore.
- 01 · The cost
Docs ship a sprint after the feature
The feature is ready on release day. The guide, the help article and the screenshots wait until someone has time.
Ask Snaplore · Ask it Guides · Follow itThe agent records it as it builds it.
When your coding agent finishes the feature, it records a walkthrough in your own environment. Snaplore turns it into the guide, the help article and the agent skill before the release.
- 02 · The cost
“How do I…?” tickets after every release
People find the new button but not how it works. Support answers the same question until the docs catch up.
Guides · Follow it Knowledge · Find itThe answer is live on release day.
The guide and the help article go live with the feature. Embed them in your help center, and support sends a link to the step instead of typing the answer.
- 03 · The cost
Every UI change breaks the docs
Rename a button or move a menu, and the screenshots and videos are wrong. Someone has to record, edit and narrate them again.
Guides · Follow itRe-record one step. The voice follows.
Snaplore flags guides that may be out of date. Re-record only the step that changed, and Snaplore rewrites and re-voices that step. The link in your help center stays the same.
From step log to voiceover.
Through one MCP tool, publish walkthrough, your coding agent sends three things. A Snaplore skill tells any coding agent how to record them.
The agent sends
-
The video
Recorded on your machine. For web apps, Playwright, the browser tool your agent already uses for testing, records it. Mobile simulators and emulators record too.
walkthrough.webm · 0:18 -
A step log
A timestamp for each action, what it did and a one-line reason.
0:06 Go to the Users tab · the new button is here -
The context
The ticket or pull request description, so the narration says what the feature is for.
PR #482 · Invite users by email
Snaplore
The walkthrough script for Invite a teammate: each step of the agent’s log, the voiceover line Snaplore wrote for it, how long the step is held, whether it matches the screen, and the voice. Step 3 first says Add member, gets flagged because the screen says Invite user, and is corrected.
Recorded where you build, before release.
Tools that record from outside your product need a login to a demo or staging account. Your coding agent records the feature where it already runs.
-
Ready on release day
The walkthrough is recorded before release, so the guide ships with the feature.
-
No logins leave your company
Snaplore never needs access to a demo or staging account.
-
Web, desktop and mobile
Localhost, internal sites, desktop apps, and mobile apps in simulators and emulators.
-
More than a video file
Each walkthrough lands in your knowledge base and as an agent skill.
Nothing goes live without a person.
-
Test accounts and sample data
The Snaplore skill tells your agent to record with test accounts and sample data only.
-
Secrets blurred
Anything that looks like a password, key or customer record is blurred before anyone sees it.
-
A person approves
Every guide, article and skill is labelled “Made by an AI agent” and waits for someone on your team.
Start from a product team template.
For your users, your support team and whoever is on call. Each comes as a blank download and as an example made from a real video.
-
Release notes
What’s new in each release, with a voiced walkthrough for every feature.
-
How-to guide
One task in numbered steps, each with a screenshot and a short clip.
-
Runbook
Deploys, rollbacks and on-call fixes, with the checks and the steps a person confirms.
-
User manual
Every feature of your product, organized by task, for your customers.
Start with one feature.
Agent-made walkthroughs come with Pro and Team. Pilots run on Enterprise and start with walkthroughs for one of your features.
-
Team
For product teams€25 per creator a monthMinimum 3 creators. Readers never pay.- Agent-made walkthroughs with voiceover Early access
- MCP for your coding agents and AI assistants
- Agent-ready guides Early access
- Knowledge: help articles linked to the moment in the video
- Workspaces, user management and approvals
-
Enterprise
For pilotsCustom quote, priced by siteReaders never pay.- Everything in Team
- Your brand on your own domain
- Export anytime
- SSO on request
Launch package: we start with walkthroughs for one of your features and produce your first 10 to 20 guides.
Book a demo
Trying it on your own first? Free has 25 recordings and 3 guides. Get Snaplore free Compare plans
Which coding agents work with Snaplore?
Any coding agent that can connect to an MCP server. A Snaplore skill tells it how to record and what to send, and one MCP tool, publish walkthrough, sends it.
How does the agent record our app?
For web apps, with Playwright, the browser tool coding agents already use for testing. Mobile simulators and emulators record too. The agent records on your machine, before release.
What does Snaplore receive?
The video, the step log and the ticket or pull request description. Snaplore never needs a login to your app. Anything that looks like a password, key or customer record is blurred.
Can we edit the script before it goes live?
Yes. Every guide, help article and agent skill waits for a person to approve it. Change a line and Snaplore voices it again, in your workspace’s voice.
What if the agent sends no step log?
Snaplore can describe a video from its screenshots alone. The step log makes the script more precise, so the Snaplore skill asks the agent to write one.
Which plan do we need?
Agent-made walkthroughs come with Pro and Team, in early access. Pilots run on Enterprise and start with walkthroughs for one of your features.