Skip to content

sase repro

Capture and replay reproduction bundles

Reference for sase repro. Run sase repro --help for the exact output on this checkout.

usage: sase repro [-h] {capture,replay} ...

Options:

Option Description Default
-h, --help show this help message and exit —

Subcommands:

Subcommand Summary
sase repro capture Capture a reproduction bundle
sase repro replay Replay a reproduction bundle through the headless TUI harness

sase repro capture

usage: sase repro capture [-h] {agents-tab} ...

Options:

Option Description Default
-h, --help show this help message and exit —

Subcommands:

Subcommand Summary
sase repro capture agents-tab Capture an Agents-tab reproduction bundle from filesystem state

sase repro capture agents-tab

usage: sase repro capture agents-tab [-h] --output OUTPUT [--commit-safe]
                                     [--no-commit-safe] [--size SIZE] [--json]

Options:

Option Description Default
--commit-safe Redact local names and paths for a shareable bundle (default) true
-h, --help show this help message and exit —
--json Emit a machine-readable JSON result false
--no-commit-safe Keep unredacted local identifiers in the capture true
--output OUTPUT Directory where agents_tab_repro.json and artifacts are written (required) —
--size SIZE Terminal size label to store with the bundle, WIDTHxHEIGHT 120x40

sase repro replay

usage: sase repro replay [-h] [--assert-stable] [--json]
                         [--write-artifacts WRITE_ARTIFACTS] [--size SIZE]
                         path

Options:

Option Description Default
--assert-stable Exit non-zero if replay invariants fail false
-h, --help show this help message and exit —
--json Emit a machine-readable JSON verdict false
--size SIZE Headless terminal size for replay, WIDTHxHEIGHT 120x40
--write-artifacts WRITE_ARTIFACTS Directory where replay screen text and SVG artifacts are written —

Arguments:

Argument Description
path Bundle JSON file or bundle directory

Related: CLI command groups.

_[project]: A sase project is a named unit of work registered with SASE. _[workspace]: A sase workspace is a numbered clone of a project's primary repo, managed by the workspace store and tracked in that project's registry.json. _[agent]: A sase agent is an agent session or a single agent that does not belong to a session. _[prompt]: A prompt is the text SASE hands to a provider to start an agent turn. _[macro]: A macro is a reusable prompt triggered with #name in agent prompts. _[Patch]: A Patch is SASE's local unit of change. _[bead]: A bead is one tracked work item in SASE's git-native issue tracker. _[plan]: A plan is a persisted, approved artifact recording the intent behind agent work. _[TUI]: The TUI is SASE's terminal interface for running agents and reviewing results. _[epic]: An epic is an executable multi-phase plan run with sase bead work. _[gate]: A sase gate is a durable, command-backed request for one user decision, created when work must pause for the user. _[monitor]: A sase monitor is a monitor turn that runs one long command under a detached supervisor, so the command outlives the agent that started it. *[stitch]: A stitch is the lightweight ordered change record inside a Patch's STITCHES: section.