How changes land¶

SASE routes completed work through a host-owned workflow that records the result and asks the active version-control provider to carry it forward.

The idea in one picture¶

Agent work ──► Host finalizer ──► VCS provider ──┬──► Commit or proposal
                                  └── Pull request ──► Patch
Commit or proposal ──► Stitches

How it works¶

After an agent turn finishes, the host's commit finalizer checks for changes and runs the selected workflow. The workflow calls the VCS provider, which handles operations for the project's version-control system.

A workflow can create a commit, save a proposal, or open a pull request. SASE records commit and proposal results as Stitches; a pull request creates a Patch that carries the review state. The agent supplies the result for the host to process, while the host owns the finalizer and the VCS operation.

When it matters¶

Choose a commit when the change belongs directly on the current branch.
Choose a proposal when you want to save a diff for later application.
Choose a pull request when another person should review the change before it merges.

Do it¶

Review and land a change — inspect an agent's result and complete its review.
Get automated code review — review each change automatically before it lands.

Look it up¶

Commit workflows — workflow behavior and finalizer details.
VCS providers — version-control operations and provider boundaries.
Patch format — the review record created for a pull request.

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