Skip to content

Review and land a change

Review the completed agent's work, then use the project's chosen workflow to record or share the change.

Before you start

You need a completed agent run and access to the project repository or pull request provider. Decide whether the change should become a commit, a saved proposal, or a pull request.

1. Choose how the result should land

Add the project's commit workflow to the agent prompt: #commit creates a commit, #propose saves a diff for later, and #pr opens a pull request. Use a pull request when someone should review the change before it merges; see the workflow reference for its required inputs.

2. Wait for the run to finish

SASE handles the selected workflow after a SASE-launched agent finishes. On the Agents tab, wait for both the agent and its finalizer to settle. Read the agent's final response and inspect the recorded result before starting another run.

3. Inspect the change

For a pull request, review its Patch and the pull request diff, checks, and discussion. For a commit, inspect the recorded commit and its changed files. Compare the result with the task and check that the reported verification covers the change you requested.

If the change needs another pass, give a follow-up agent a clear correction and cite the result you reviewed. See Hand a result to another agent.

4. Complete the review

Merge a pull request only after its review and checks are complete. A commit workflow already records its commit on the configured branch; a proposal remains saved for you to apply when it is ready.

If it goes wrong

If the agent completed but no commit, proposal, or pull request appears, inspect the finalizer status on the Agents tab and follow its error before retrying. The workflow reference explains the result records and recovery details.

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