sase sudo¶
Request, inspect, and answer typed sudo gates
Reference for sase sudo. Run sase sudo --help for the exact output on this checkout.
usage: sase sudo [-h] {answer,exec,finalize,list,request,show} ...
Create typed sudo request gates and answer them from a controlling terminal through the dedicated sudo runner.
Bare sase sudo defaults to sase sudo list.
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
Subcommands:
| Subcommand | Summary |
|---|---|
sase sudo answer |
Approve or deny one sudo gate |
sase sudo list |
List sudo gate turns |
sase sudo request |
Create a sudo gate from one JSON object on stdin |
sase sudo show |
Show a sudo gate |
sase sudo answer¶
usage: sase sudo answer [-h] [-a | -d | -u] [-c ID] [-D | -N] [-f FEEDBACK]
[-j] [-R | -r]
ID
Options:
| Option | Description | Default |
|---|---|---|
-a, --approve |
Approve and run | false |
-c ID, --command ID |
Reviewed command id to run; repeat to select a subset | — |
-d, --deny |
Deny | false |
-D, --detach |
Authenticate on this TTY, then run the reviewed commands in a supervised background proc; the gate stays pending until that proc finishes (the default for approvals) | false |
-f FEEDBACK, --feedback FEEDBACK |
Reviewer note | — |
-h, --help |
show this help message and exit | — |
-j, --json |
Emit JSON | false |
-N, --no-detach |
Authenticate and run in the foreground | false |
-R, --restart |
Restart a partial attempt | false |
-r, --resume |
Resume a partial attempt | false |
-u, --run |
Authenticate and run | false |
Arguments:
| Argument | Description |
|---|---|
gate_ref |
Sudo gate id or shell ref |
sase sudo list¶
usage: sase sudo list [-h] [-a] [-j] [-l LIMIT] [-p PROJECT]
Options:
| Option | Description | Default |
|---|---|---|
-a, --all |
Include settled gates | false |
-h, --help |
show this help message and exit | — |
-j, --json |
Emit JSON | false |
-l LIMIT, --limit LIMIT |
Limit rows | — |
-p PROJECT, --project PROJECT |
Filter by project | — |
sase sudo request¶
usage: sase sudo request [-h] [-j] [-o ORIGIN_AGENT]
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
-j, --json |
Emit JSON | false |
-o ORIGIN_AGENT, --origin-agent ORIGIN_AGENT |
Attribute the request | — |
sase sudo show¶
usage: sase sudo show [-h] [-j] ID
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
-j, --json |
Emit JSON | false |
Arguments:
| Argument | Description |
|---|---|
gate_ref |
Sudo gate id or shell ref |
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.