Skip to content

Reuse a prompt with macros

Save a useful prompt as a macro when you want to start future tasks with the same instructions.

Before you start

You need a prompt that has worked at least once and is useful in more than one run. Remove details that belong only to one task, and make changing values easy to identify.

1. Load the prompt you want to reuse

Open the prompt in SASE's TUI. For a prompt that has already run, find it in History and load it into the prompt bar as a draft. For an unsent draft, keep it in the prompt bar. See Find and replay an old prompt for the History steps.

2. Save it as a macro

In the prompt bar, use Ctrl+G X to open the save panel. Choose a project location when the prompt belongs to one repository, or a home location when you want it across projects. Give it a short name that describes what it does and save it.

3. Use the macro in a prompt

Type #<name> where you want the saved instructions to appear, replacing <name> with the name you chose. Add the details for this run, then review the prompt before launching. Macro arguments and expansion rules are listed in the Macro reference.

If it goes wrong

If the macro does not appear in completion, check the location where you saved it and that the prompt uses its exact name. Browse the macro catalog to see the discovered name and preview its definition.

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