sase file-hook¶
Inspect configured per-file repository hooks
Reference for sase file-hook. Run sase file-hook --help for the exact output on this checkout.
usage: sase file-hook [-h] <subcommand> ...
Inspect non-gating commands configured under file_hooks and the producer audit history for matching, dispatch, and pre-run failures. With no subcommand, sase file-hook defaults to sase file-hook list.
Bare sase file-hook defaults to sase file-hook list.
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
Subcommands:
| Subcommand | Summary |
|---|---|
sase file-hook exec-batch |
— |
sase file-hook history |
Show recent producer dispatch audits |
sase file-hook list |
List effective file hooks and their config sources |
sase file-hook show |
Show one producer dispatch audit |
sase file-hook exec-batch¶
usage: sase file-hook exec-batch [-h]
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
sase file-hook history¶
usage: sase file-hook history [-h] [-j] [-n N]
List producer-side file-hook outcomes newest first: dispatched batches, filter misses, no configured hooks, and producer failures. Command-run failures still live on batch run logs; this surface is the pre-run evidence. This is not the default for bare sase file-hook.
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
-j, --json |
Emit deterministic machine-readable JSON | false |
-n N, --limit N |
Maximum number of audits to show (default: 20; 0 means all) | 20 |
sase file-hook list¶
usage: sase file-hook list [-h] [-j]
List every valid effective file hook with its command, filters, timeout, description, and contributing config layer. Invalid entries are warned about and skipped. This is also the default for bare sase file-hook.
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
-j, --json |
Emit deterministic machine-readable JSON | false |
sase file-hook show¶
usage: sase file-hook show [-h] [-j] audit_id
Print one producer audit by exact id or unique prefix so an operator can tell whether an event was unmatched, dispatched, or failed before a hook command ran.
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
-j, --json |
Emit deterministic machine-readable JSON | false |
Arguments:
| Argument | Description |
|---|---|
audit_id |
Producer audit id, or a unique prefix of that id |
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.