Skip to content

sase file-history

Inspect and modify the file-reference history

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

usage: sase file-history [-h] {delete,list} ...

Bare sase file-history defaults to sase file-history list.

Options:

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

Subcommands:

Subcommand Summary
sase file-history delete Remove one entry from the file-reference history
sase file-history list Print the recency-ordered file-reference history as a JSON array

sase file-history delete

usage: sase file-history delete [-h] -p PATH

Options:

Option Description Default
-h, --help show this help message and exit —
-p PATH, --path PATH Path entry to remove (must exactly match the stored value) (required) —

sase file-history list

usage: sase file-history list [-h]

Options:

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

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.