Reference¶
Exact SASE facts; guides teach workflows.
CLI¶
- CLI behavior notes — root command behavior and routing
- CLI command groups — generated flags and subcommands
- Diagnostics and support reports — validation and support commands
- Query language — filtering runs and beads
Configuration¶
- Configuration keys — generated key paths, types, defaults
- Configuration files and behavior — file layout, merge order, runtime details
TUI¶
- TUI — tabs, prompt, Launch Control, pager, and keys
- SASE Admin Center
- TUI keymaps
- SASE Pager
Macros and workflows¶
- Macros — reusable prompts and directives
- Directive catalog — generated syntax and arguments
- Macro discovery order — file-backed definitions by priority
- Workflows — multi-agent workflow files
Work units¶
- Work units — plans, beads, goals, Patches, and ProjectSpec
- Plans — saved work proposals and decisions
- Beads — git-portable work and dependency records
- Patches — review records for changes
- Goals — durable outcome records
- ProjectSpec — project metadata and Patch records
Agents and workspaces¶
- Agents and workspaces — sessions, setup, synchronization, and workspace storage
- Agent output variables — published values from agent runs
- SASE disk cleanup — inspect and clean up SASE-created bytes
Version control¶
- Version control — providers and commit workflows
Automation¶
- Automation — notifications, scheduling, monitors, and related tools
Providers¶
- Providers and models — provider integration and model routing
- Agent CLIs — supported CLIs and install management
- Models and aliases — catalog, tiers, reasoning effort, and aliases
- Provider routing — temporary overrides, disables, and priority
Memory¶
- Memory — durable agent context and instruction documents
- Memory details — memory types, webs, and audited reads
- Instruction bundles — generated agent instructions
- Memory history — how memory changed
Prompts and artifacts¶
- Prompt history — replaying past prompts
- Artifact references — citing records in prompts
- Artifact links — typed links between records
Integrations¶
- Integrations — plugins, editor, completion, mobile, and remote dispatch
Content layout and upgrading¶
- Content layout — canonical paths
- Upgrading — upgrade notes
Glossary and decisions¶
- Glossary — every SASE term, generated
- Design decisions — why SASE works this way
_[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.