Agents and workspaces

Reference pages describe agent sessions, setup, workspace storage, and shared hood data.

Sessions and groups

• Agent clans — parallel agent groups.
• Agent sessions — sequential chains of agent turns.
• Agent tribes — user-managed agent groups.
• Agent-initiated launches — sessions started by an agent.
• Agent holds — admission barriers for agents and undispatched procs.
• Agent output variables — published values and downstream reads.

Workspace and initialization

• Workspaces — workspace storage and commands.
• Initialization — project setup commands.
• Service host initialization — per-user service host setup.
• Machine initialization — remote machine enrollment.
• Memory initialization — memory setup and audit commands.

Shared data and other topics

• Agent hood synchronization — shared hood data and publication.
• Agent auto-restart — update-skew recovery.
• Agent revive log — revival audit records.
• Runner slots — queued agent admission.
• Agent providers — supported agent CLIs.
• Agent attachments — images agents can see.
• Instruction bundles — generated agent instructions.
• Mentors — automated code review.
• Remote dispatch — running agents on another machine.

Related

• Reference — all reference sections.

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