Prompts, macros, and workflows

A prompt tells an agent what to do; macros and workflows let you reuse and organize that direction.

The idea in one picture

Prompt ──► Agent turn
   ▲
   ├── Macro: reusable prompt content
   └── Workflow: an ordered process around agent work

The diagram shows how a direct request can use a macro or become part of a larger workflow.

How it works

A prompt gives an agent the task for one turn. A macro names prompt content you can reuse, and can take inputs to adapt the same instructions to different work. A workflow groups steps into a repeatable process, combining prompts with actions, branches, or approval points when the task needs them.

These forms keep the task's purpose visible while avoiding repeated instructions. Use the smallest form that fits: a direct prompt for one task, a macro for reusable wording, and a workflow when several steps need to run together.

When it matters

• Write a direct prompt when the task is specific to this agent turn.
• Reuse a macro when the same direction comes up across tasks.
• Use a workflow when work needs an ordered sequence or a checkpoint.

Do it

• Get started with SASE — launch a first agent with a task prompt.
• Reuse a prompt with macros — keep useful instructions for later runs.
• Find and replay an old prompt — search and reuse prompt history.

Look it up

• Macros — macro syntax, inputs, and expansion behavior.
• Workflow specification — workflow steps and control flow.
• Glossary — macro, invocation, and workflow terms.

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