Tome Robot — explain it to me
A knowledge base that watches your team work
and updates itself when your software changes.
Record a few walkthroughs. Tome Robot turns every click into a searchable, narrated, self-maintaining KB — and flags stale docs the moment a UI changes, so the answers you write today are still right a year from now.
No credit card. Start recording in under two minutes.
The loop
Your team captures walkthroughs with the Chrome extension. Every click becomes a screenshot, a narrated step, and a record of exactly what was clicked — by name, not by pixel.
Tome Robot transcribes, cleans fillers, grounds each step in the real UI, and builds a graph of every screen your tools have.
Ask a question in plain English. Get a step-by-step answer with real screenshots — even for paths nobody recorded directly.
When the UI changes, Tome Robot notices. Articles are flagged, drafts are auto-generated, nothing silently rots.
What you get
The short version: a help center that keeps itself honest. The longer version is below.
Every answer cites the exact step, screenshot, and recording it came from. No hallucinated UI elements.
Every night, Tome Robot compares the screens in your articles to what's actually live. Anything that's moved, renamed, or disappeared gets flagged before a customer hits it.
Dictionary + vision detectors blur PII in screenshots automatically. Approve or reject in a single click.
Split articles by audience. Public ones live at your own domain; internal ones stay gated behind SSO.
Upload a logo, pick colors, done. Your KB inherits the look without a frontend engineer.
Pipe new articles into Slack, Notion, or your helpdesk. Webhooks fire on publish, drift, and approval events.
Built for
Turn every screen-share into a searchable answer. Stop solving the same ticket twice.
New hires get a personal walkthrough of your internal tools — not a stale wiki.
Auto-generate in-app help from real user paths. Ship features without writing a doc.
vs. a traditional KB
Regular knowledge bases assume somebody will sit down and write them. Regular knowledge bases are wrong about that.
| Feature | Tome Robot | Typical KB |
|---|---|---|
| Written from scratch | No — recorded from real work | Yes, manually |
| Updates when UI changes | Detected automatically | When someone notices |
| Screenshots | Captured on every step | Pasted in, rot fast |
| Q&A | Grounded in recordings | Full-text search |
| Who writes it | Your team, by doing their job | A writer you don't have |
Common questions
No. You record walkthroughs, Tome Robot writes the articles. You review and publish.
Nightly scans hash every captured screen. If an article's screenshot no longer matches reality, it's flagged and a draft update is auto-generated.
Yes. Record against any web app behind your SSO. Articles can be marked internal and stay gated.
Stop writing docs nobody reads.
Record them instead.
Grab an invite, install the extension, walk through the tool you're tired of explaining. Tome Robot does the rest.