sase pager¶
Read refs, paths, or stdin in the SASE link-traversing pager
Reference for sase pager. Run sase pager --help for the exact output on this checkout.
usage: sase pager [-h] [-c {auto,always,never}] [-l {auto,never}] [-p]
[-s ALIAS] [-t TITLE] [-w WIDTH]
[REF|PATH ...]
Open artifact references, file paths, or stdin as one navigable SASE pager document. With redirected stdout, --plain, or no controlling terminal, the command writes plain text instead of starting the Textual app.
Options:
| Option | Description | Default |
|---|---|---|
-c COLOR, --color COLOR |
Color output: auto, always, or never (default: auto) (choices: always, auto, never) |
auto |
-h, --help |
show this help message and exit | — |
-l LINKS, --links LINKS |
Link scanning and painted keys: auto or never (default: auto) (choices: auto, never) |
auto |
-p, --plain |
Dump plain text without starting the pager | false |
-s ALIAS, --syntax ALIAS |
Highlighting language: auto, none, or a Pygments alias (default: auto; config pager.syntax). Invalid aliases fail before stdin is read; text/plain skip the language chip | — |
-t TITLE, --title TITLE |
Document title for stdin input | — |
-w WIDTH, --wrap WIDTH |
Wrap prose at WIDTH columns; accepts 'auto', 'none', or 0 (default: 88) | 88 |
Arguments:
| Argument | Description |
|---|---|
inputs |
Artifact reference or file path to add as a section; omit or pass '-' by itself to read stdin |
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.