Skip to content

Local-First Demo Recording for Product Teams

Great demos are hard to repeat. Local-first recording makes them much easier.

Local-first means your recording workflow runs on your machine first, helping reduce accidental data exposure.

This guide shows how product teams can use Gasoline Agentic Devtools to create reliable demos.

  • Local-first: Data and tooling run primarily on your own device.
  • Playback: Re-running a recorded sequence.
  • Demo script: Structured sequence of interactions for a repeatable story.

You want demos that are:

  • repeatable,
  • easy to update,
  • safe to share.

Step-by-Step with Gasoline Agentic Devtools

Section titled “Step-by-Step with Gasoline Agentic Devtools”
configure({what: "recording_start"})

Use clear, intentional interactions.

configure({what: "recording_stop", recording_id: "rec-demo-v1"})
configure({what: "playback", recording_id: "rec-demo-v1"})
observe({what: "playback_results", recording_id: "rec-demo-v1"})

Step 5. Capture a polished reproduction script

Section titled “Step 5. Capture a polished reproduction script”
generate({what: "reproduction", include_screenshots: true})
  • Keep one recording per narrative (“new user signup”, “dashboard insights”).
  • Avoid live dependencies you cannot control.
  • Use deterministic test data where possible.

[Image Idea] Demo timeline with chapter markers for each product moment.

[Diagram Idea] Demo production flow: record -> review -> replay -> export script.

With Gasoline Agentic Devtools, demos stop being one-off performances and become reusable, improvable artifacts.