Show it once. Hand over the whole story.

A walkthrough records your screen, or one window, while you talk it through. You get a screenshot at every step, what you said around it, a line for every click and page, and private details blurred. Share it as a link, or hand the folder to an agent.

Paste into Terminal
curl -fsSL https://capture.startwellventures.com/install.sh | bash

It downloads the latest version, checks it, and puts Startwell Capture in Applications. Before macOS 26 it also fetches the speech model. Run it again any time to update. Read the script first, or download the .dmg.

A walkthrough, replayed

Demo: card declined at checkout

Step 1: Your basket — Demo Shop

Step 1 · 00:02 demoshop.example/basket · recording started

  1. Chapter · Your basket — Demo Shop
  2. 00:00 · Opened Google Chrome — "Your basket — Demo Shop" (demoshop.example/basket)
  3. Jo · 00:01Okay, this is Demo Shop. I'm on the basket page with one blue mug.
  4. 00:02Step 1screenshot · recording started
  5. 00:09 · Clicked menu "Quantity" in "Blue mug"
  6. Jo · 00:09I'll make it two.
  7. 00:11Step 2screenshot · click (after it settled)
  8. Jo · 00:15Then on to checkout.
  9. 00:16 · Clicked link "Go to checkout"
  10. 00:17 · Navigated to demoshop.example/checkout — "Checkout — Demo Shop"
  11. Chapter · Checkout — Demo Shop
  12. 00:18Step 3screenshot · page changed (after it settled)
  13. Jo · 00:20My email and address are already filled in from last time.
  14. Jo · 00:34I put in the test card, four two four two, and the expiry.
  15. 00:36 · Clicked into field "Card number"
  16. Jo · 00:44And pay now.
  17. 00:45Step 4screenshot · click (just before)
  18. 00:45 · Clicked button "Pay now"
  19. Jo · 00:49And it says my card was declined. That's the test card, so it shouldn't be.
  20. 00:51 · Navigated to demoshop.example/checkout/payment — "Payment failed — Demo Shop"
  21. Chapter · Payment failed — Demo Shop
  22. 00:52Step 5screenshot · page changed (after it settled)
  23. Jo · 00:59I think it's the postcode. It has a space in it. Without the space it goes through.
  24. 01:08 · Opened Slack — #checkout
  25. Jo · 01:10That's it. I'm sending this over.

A walkthrough of the fictional Demo Shop, replayed three times faster than it was recorded. Hover to pause, or pick a step. The same recording as a share page and as a pack to download.

How a walkthrough is made

Ten steps below, in four stages. Everything up to sharing happens on your computer. Keys are the macOS ones; on Windows and Linux ⌘⇧ is Win+Shift or Super+Shift, but a screenshot is Win+Alt+Shift+S or Super+Alt+Shift+S, and ⌥⌘⇧U is Win+Alt+Shift+U or Super+Alt+Shift+U.

On macOS, four permissions, checked live

  • Screen Recording to see the screen or window you pick. Required. macOS applies it after a quit and reopen, so the button is right there.
  • Microphone for your narration.
  • Accessibility for window titles and the names of what you click.
  • Automation to ask your browser which page it is on.

The list checks itself every two seconds, so it turns green as you switch each one on.

That is macOS. Windows asks for none of these; only the microphone has to be switched on for apps in its Settings. On Linux with Wayland, your desktop asks which screen to share the first time, and after that only if it can’t remember the choice.

The permissions checklist: Screen Recording is off with Open Settings and Quit and reopen buttons; Microphone, Accessibility and Automation are on.

Pick what to record

The whole screen is chosen to start with. Or choose one window from the list (on macOS an app too, or the macOS picker), and only that window is captured: other windows, the menu bar or taskbar and notifications stay out. On Linux with Wayland, your desktop’s own dialog chooses what is shared.

Give it a title and a topic. Screen video is on by default alongside the screenshots, and can be turned off.

The What to record step: a window list, a title field, a topic and a Video switch. Here Screen Recording is not on yet, so the app explains how to turn it on.
Shown before Screen Recording was switched on: the app says so plainly and offers the fix.

Record and talk

Use the app as you normally would and say what you are doing. A card at the top right of the screen shows that it is recording, the time and the number of steps. Pause it when you need to, and stop with ⌘⇧U.

Something worth a screenshot that the app would not notice? Press ⌘⇧S to mark a step by hand.

While recording
⌘⇧U    start from any app (⏎), and stop
⌘⇧S    mark a step now
⌥⌘⇧U   pause or resume

A small card stays at the top right:
Recording · 01:12 · 4 steps
[ Pause ]  [ Mark step ]  [ Stop ]

Screenshots take themselves

The screen is sampled twice a second. A step is kept only when the screen has really changed, so a blinking cursor or a spinner does not make one.

The app keeps the last few frames, so it can save the screen as it was just before a click or a page change, as well as after. The “after” shot waits until the page stops moving, up to three seconds. A “before” frame is skipped when nothing changed since the last step.

Steps are at least two seconds apart and at most twenty a minute. Near-duplicates are dropped.

A step is taken whenWhich frame
You start recordingThe first frame
The page address changesJust before, and once it settles
You switch app or windowJust before, and once it settles
The window title changesJust before, and once it settles
You click inside the windowJust before, and once it settles
Most of the screen changesOnce it settles
You press ⌘⇧SThat moment
You stopThe last frame, if it is new

Every click and page becomes a line

While it records, the app notes what you do: which app and window, which page, and what you clicked, by its name. These lines are woven into the transcript in italics, so the words and the actions read in one order.

The README turns them into a numbered What I did list: repro steps written by the app, with no AI involved. Typed text is never recorded. Clipboard lines are off unless you turn them on.

transcript.md
_00:00 · Opened Google Chrome — "Your basket — Demo Shop" (demoshop.example/basket)_

**Jo** · 00:01
Okay, this is Demo Shop. I'm on the basket page with one blue mug.

_00:09 · Clicked menu "Quantity" in "Blue mug"_
_00:36 · Clicked into field "Card number"_
_00:45 · Clicked button "Pay now"_
_00:51 · Navigated to demoshop.example/checkout/payment — "Payment failed — Demo Shop"_

Private details are blurred

When you stop, the app reads the text in every screenshot on your computer and blurs what looks private:

  • Email addresses
  • Card numbers (ones that pass the card checksum)
  • Phone numbers

A screenshot taken while a password field was in use is left out of the pack, where the system can tell. If a screenshot’s text can’t be read, it waits for you to approve it. You see all of this in review before anything leaves your computer.

A Demo Shop checkout page with the email address and card number blurred.
Step 4 of the demo pack, with the email and card number blurred the way the app blurs them.

Review every step

The check screen tells the recording stage by stage, with every click and screenshot between your words. Click a line to see its screenshot. Leave any screenshot out of the pack, or add a blur where you want one.

Steps you leave out stay on your computer and never reach the pack. Nothing is shared until you finish review.

Checking a walkthrough: a row that checks the topic, 5 screenshots with 1 left out, 0 blurs and the voices; the recording stage by stage with words, clicks and screenshots in order; the selected screenshot with Leave out of the pack and Add a blur; every screenshot below it.
  1. Check before you hand it on: topic, screenshots, blurs, voices.
  2. Clicks and screenshots sit between your words.
  3. Leave out a screenshot, or add a blur.
  4. Hand off, files or a share link, once it looks right.

A folder, a link or a zip

Finishing review writes the context pack and puts its path on your clipboard.

To share it with someone, upload it for a link. Anyone with the link can open the walkthrough in a browser: chapters, steps, the transcript and the video. Uploading needs an invite code from Startwell. Without one, export a zip instead.

Open the demo’s share page

After review
Context pack
  ~/Startwell Capture/Demo Shop/2026-11-03 1402 Demo card declined at checkout/
  
  Share link (needs an invite code)
  https://capture.startwellventures.com/w/<id>
  
  Zip
  The same folder as one file, for email or chat.
Step 5 of the demo: the Demo Shop payment page saying the card was declined.
steps/005.png
steps.md
### Step 5 · 00:52 · Payment failed — Demo Shop

![Step 5](steps/005.png)

- **App:** Google Chrome
- **Window:** Payment failed — Demo Shop
- **URL:** https://demoshop.example/checkout/payment
- **Captured:** page changed (after it settled)
- **Said:** And it says my card was declined…

Hand it to Claude Code

The path is already on your clipboard. Paste it into Claude Code, or any agent that can read files, and ask. The README tells the agent what to open next.

Connected the topic to a project? The agent can also find the pack itself through agent access.

Claude Code
> Read ~/Startwell Capture/Demo Shop/2026-11-03 1402 Demo card declined at checkout/README.md
  and fix the bug it shows.

Reads README.md, then steps.md and the screenshots it links.
"What I did" gives it the repro steps; transcript.md gives it
why the tester thought it was the postcode.

Sending one to a tester?

There is a plain-language guide for people who have never used the app: what to install, what to click, and what is and is not recorded.