Skip to content

Find and replay an old prompt

Search prompt history to find a previous task, inspect it, and launch it again or edit it first.

Before you start

You need a prompt that SASE recorded from an earlier run. Check its project and workspace target before you replay it so the new run goes to the right place.

1. Open prompt history

In SASE's TUI, press Ctrl+K in the prompt bar or ,. from a main tab to open History. Search for a distinctive phrase from the prompt. Use the project filter when several projects have similar prompts. Press Ctrl+J to load older history when the prompt is not in the current page.

2. Inspect the prompt before launching

Select a history row to read its full prompt. Press Tab to load it into the prompt bar as a draft, then update its workspace target or task details if they have changed. Press Enter and confirm the launch action when the prompt is ready.

Pressing Enter on a history row submits it directly. Load it with Tab first when you want to review or edit it before it runs.

3. Use the shell when you prefer a command

Run sase prompt list to see recent prompts, then use sase prompt run <id> -e to open one in an editor before launching. The prompt reference lists search, filter, replay, and cancellation options.

If it goes wrong

Cancelled prompts are hidden from the normal History list. Show cancelled prompts in the overlay with Ctrl+X, or use the cancelled filter in the shell when you are recovering an unlaunched prompt.

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