sase usage¶
Inspect and refresh cached LLM subscription usage
Reference for sase usage. Run sase usage --help for the exact output on this checkout.
usage: sase usage [-h] {list,refresh} ...
Inspect cached provider subscription-usage observations and submit explicit refreshes. Running sase usage defaults to sase usage list. The list command never calls provider CLIs or APIs; use sase usage refresh to submit bounded refresh work.
Bare sase usage defaults to sase usage list.
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
Subcommands:
| Subcommand | Summary |
|---|---|
sase usage list |
List cached subscription usage without probing providers |
sase usage refresh |
Submit explicit subscription-usage refresh work |
sase usage list¶
usage: sase usage list [-h] [-j] [-P] [-p PROVIDER] [-v]
Render the cached subscription-usage snapshot. This command is strictly offline and does not start AXE, log in, or call provider CLIs. Missing observations are reported as data.
Options:
| Option | Description | Default |
|---|---|---|
-h, --help |
show this help message and exit | — |
-j, --json |
Emit one stable JSON document | false |
-P, --plain |
Emit undecorated line-oriented text | false |
-p PROVIDER, --provider PROVIDER |
Filter to one provider; repeatable | — |
-v, --verbose |
Show source, diagnostic, and exact timestamp details | false |
sase usage refresh¶
usage: sase usage refresh [-h] [-b] [-j] [-P] [-p PROVIDER] [-v]
Submit bounded durable refresh work for provider subscription usage. By default this waits for submitted or joined work and then renders the refreshed cache. Use --background to return after submission.
Options:
| Option | Description | Default |
|---|---|---|
-b, --background |
Submit or join refresh work and return without waiting | false |
-h, --help |
show this help message and exit | — |
-j, --json |
Emit one stable JSON document | false |
-P, --plain |
Emit undecorated line-oriented text | false |
-p PROVIDER, --provider PROVIDER |
Filter to one provider; repeatable | — |
-v, --verbose |
Show source, diagnostic, and exact timestamp details | false |
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.