Skip to content

Schedule recurring work

This guide puts a repeated check on a schedule: a routine that ticks on an interval and a job script that does the work. It assumes the check already exists as an executable script; if the work needs a person to decide each time, keep it as a gate instead.

Before you start

You need a checkout where sase runs and a script the scheduler can find through the configured job script directories. Confirm the scheduler is running first:

sase scheduler status

Start it when the status says otherwise; nothing scheduled runs while it is stopped.

1. Add a routine and a job

Declare the lane and its cadence in the configuration file under the scheduler section. Every routine and every job needs a one-line description of what it owns:

axe:
  routines:
    nightly_checks:
      description: |-
        Run inexpensive project checks once an hour
      interval: 3600
      jobs:
        lint_scan:
          description: |-
            Scan the tree for new lint findings

            Runs the fast linter and proposes a fix agent when findings appear.
          run_every: "1h"

A job originates scheduled agent work only through its script's structured launch proposals; prompts embedded in configuration are rejected. See the scheduler reference for timeouts, triggers, and per-target expansion.

2. Run the job once by hand

Execute the job in the foreground and preview what it would launch before it runs on its own:

sase axe job run lint_scan -n
sase axe job run lint_scan

The preview run prints the validated proposals without launching agents. The real run records history under the routine so the next scheduled tick continues from it.

3. Confirm the schedule holds

List the configured jobs and re-check the scheduler after one interval has passed:

sase axe job list
sase scheduler status

The job appears with its routine and cadence, and its run history shows the manual run followed by scheduled ones.

If it goes wrong

A job missing from the list usually means its script is not discoverable or its configuration failed validation: run sase axe job doctor and fix the reported path. For a run that never starts, see Unstick a queued agent.

_[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.