sase revive-log

Show recent agent revive attempts from the audit log

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

usage: sase revive-log [-h] [--all] [--limit LIMIT] [--since SINCE]
                       [--outcome {success,failure}] [--json | --jsonl]

Options:

Option	Description	Default
--all	Show every record in events.jsonl (default: most recent 20)	false
-h, --help	show this help message and exit	—
--json	Emit one JSON object per line for machine consumption	false
--jsonl	Alias for --json	false
--limit LIMIT	Maximum number of records to show (default: 20)	20
--outcome OUTCOME	Filter by outcome (choices: failure, success)	—
--since SINCE	Only show records on/after this date (same grammar as 'sase logs')	—

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.