Automation¶
This section is the lookup home for SASE notifications, scheduling, monitors, named tools, mentors, and sudo requests.
Notifications¶
- Notifications — view and manage notifications.
- Notification types — notification payloads and fields.
- Notification tags — notification tab tags and presentation.
- Notification CLI — notification commands.
- Command-backed interaction gates — gate behavior and lifecycle.
- Notification storage — how notifications are stored.
Scheduler¶
- Scheduler — scheduler lifecycle, CLI, and host integration.
- Default scheduler routines — built-in routine behavior.
- Scheduler housekeeping — housekeeping routine details.
- Scheduler configuration — global and routine settings.
- Scheduler description grammar — routine descriptions.
- Scheduler jobs — script jobs, runs, and service views.
Other automation¶
- Monitors — start a supervised command and follow its result.
- Monitor operations — inspect monitors and see them in the TUI.
- Named tools and ToolRuns — declare and run named tools.
- Mentors — automated code review for Patches.
- Sudo requests — request and review privileged commands.
Related¶
- Reference — the product reference hub.
- Automation migration notes — scheduler naming and other upgrade notes.
_[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.