sase pipe¶
Hand this agent's turn to the next agent session member and end this turn
Reference for sase pipe. Run sase pipe --help for the exact output on this checkout.
usage: sase pipe [-h] [-f] [-j] [-m MODEL] [-n TOKEN] [-r TEXT] PROMPT
End this agent's turn and continue the run as the next agent session member in the same workspace, with the prompt you write. This is not a launch, a monitor, or fan-out: one successor, serially, in the same process. This command kills the calling agent; say everything the successor needs inside PROMPT.
Options:
| Option | Description | Default |
|---|---|---|
-f, --fresh |
Successor starts with a clean context window (default: prefix #fork: |
false |
-h, --help |
show this help message and exit | — |
-j, --json |
Print a machine-readable hand-off summary instead of the rich one | false |
-m MODEL, --model MODEL |
Model or alias for the successor (opus, opus@high, sonnet, codex/gpt-5). Default: inherit this agent's model | — |
-n TOKEN, --name TOKEN |
Successor role token: review yields |
— |
-r TEXT, --reason TEXT |
One-line reason, recorded on the successor and shown in agent lists | — |
Arguments:
| Argument | Description |
|---|---|
prompt |
Full successor prompt; % directives and # references stay live |
Related: CLI command groups.
_[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.