Fixtureframe CLI

Product experiences as code.

Record, replay, parameterize, version, and automate product experiences from your development workflow.

The same verified Fixtureframe Flow — now scriptable and automatable.

~/acme-app

$ ff run --environment staging
claimed run 4471
resolving targets      ok
executing journey      5/5 steps
capturing states       14 files
✓ flow_ac91 verified · outputs ready

Why the CLI

Product experiences should move with the product.

When software ships through code, CI, preview environments, and automated tests, the experiences that explain it should be able to participate in the same workflow.

Treat the product journey as something you can run — not something you have to recapture manually.

01Code and preview environment

02Fixtureframe CLI

03Verified run

04Customer-facing outputs

Core workflow

Record. Replay. Automate.

01Record a journey against the running application.journey captured · 5 steps

02Preserve it as a Fixtureframe Flow.flow_ac91 saved

03Parameterize the journey for approved environments or data profiles.environment: staging

04Replay and verify the flow.run 4471 · 5/5 steps · ok

05Generate the customer-facing experience from the successful run.outputs ready

Engineering surface

Built for the way engineering teams work.

21 commandsCLI command surface21 commands across the current product.

Cloud or self-hosted executionChoose the runtime model that fits the environment.

CI supportIntegrate Fixtureframe into automated workflows.

Run IDs & auditabilityPreserve execution lineage.

Secret-store integrationCredentials stay in the appropriate execution environment.

blocked by defaultProduction safetyProduction execution is blocked by default.

Verification

Execution is the truth.

A flow is useful because it can be run against the application — not because an AI or editor says the journey should work.

If the application does not behave as expected, the run fails. Only successful observed behavior becomes the basis for a reusable product experience.

run 4471 · staging✓ verified

resolving targets      ok
executing journey      5/5 steps
capturing states       14 files
✓ flow_ac91 verified
outputs ready

run 4472 · staging✕ failed

resolving targets      ok
executing journey      stopped at step 03
✕ application did not respond as authored
nothing captured
nothing published

Automation

Designed for automation.

Use Fixtureframe from development and CI workflows today.

The long-term direction is a product-experience pipeline that can stay increasingly close to software delivery.

Built for automation

development → ff run → verified run

Runs are driven by your workflow, with run IDs preserved for audit.

Three interfaces. One verified flow.

One platform

StudioBuild visually.Explore Studio → CLIProduct experiences as code.Explore the CLI → Authoring AgentDescribe what you want.Explore the Agent →

Bring product experiences into your development workflow.

Run Fixtureframe from the CLI and keep the real application at the center of every experience.

Get started Read the docs

$ ff run --environment staging