STEP-BY-STEP GUIDES THAT VERIFY THEMSELVES

Your docs shouldn't need a search party.

Walkabout walks through your app, writes the how-to guide — screenshots, callouts, captions — and re-walks the route every time you ship. If a step breaks, you hear it first. Not your customers.

Start walking $ brew install walkabout
  • one sentence in — no scripting, no step-by-step recording
  • replay is deterministic — no LLM, no per-run cost
  • you own the output
  • web + native macOS apps

Write a guide once. It stays correct on its own.

Every guide is backed by a flow — a semantic recording of the route. The loop keeps it honest:

  1. Author

    You write one sentence — "show how to invite a teammate." The agent walks the route and works out every step itself, each with a durable semantic resolver.

  2. Replay

    The flow re-runs deterministically. No LLM in the loop, so replays cost nothing and never improvise.

  3. Verify

    Every step reports unchanged, changed, or broken — in CI, on a schedule, or on demand.

  4. Publish

    Accepted runs render to Markdown + PNGs in your repo and portable HTML. Host anywhere, or on walkabout.run.

  5. Heal

    When the product drifts, the agent replays to the break, re-finds the target, and patches the step.

when the product changes, freshness catches the drift and healing patches the route — the loop closes itself

Built like a survey kit, not a screen recorder.

  • Executable guides

    A guide is a flow you can run, not a stack of stale screenshots. If it renders, it worked — end to end, today.

  • Self-verifying freshness

    Scheduled sweeps and CI exit codes (0 clean · 1 changed · 2 broken) mean a wrong guide fails the build before a reader sees it.

  • Materials, not lock-in

    Output is Markdown, PNGs, and self-contained HTML in your own repo. Put it in your help center, your app, anywhere. Leaving is easy — that’s the point.

  • Native apps too

    WebKit for the web, accessibility APIs for macOS apps, iOS on the roadmap. Recorder tools stop at the browser; we don’t.

  • Session injection

    Log in once in a visible window. We keep the session, encrypted, on your runner — and never touch a third-party login page.

  • Safe with real data

    Reset hooks reseed state before creation guides. Mutating steps are marked, dry-runnable, and blocked on production by default.

See every capability

THE HONEST SECURITY STORY

We never automate your login page.

You log in once, in a visible window on your own Mac — magic link, Google SSO, whatever you use. Walkabout keeps only the resulting session, encrypted on your machine, never in git. Runners connect outbound-only: no inbound ports, nothing exposed, so guides can run against internal and staging apps too.

  • secrets live in the Keychain — flows hold names only
  • nothing leaks into guides, reports, or screenshots
  • production refuses mutating replays without an override

RUNNER · OUTBOUND ONLY

$ walkabout runner pair WB-7KTM-R2NQ
paired to TravelSynch
pulling jobs · pushing artifacts · 0 ports open

See a real walkthrough.

A nine-step signup guide: authored by an agent, replayed on every push, rendered as portable HTML and Markdown you own.

View the example