Skip to content

Agent hood synchronization upgrades

This page records compatibility notes for earlier hood synchronization formats.

Legacy v1 limitations

V1's top-level manifest and agents/<machine-qualified-name> files remain in place and read-only. A v1 row has no trustworthy username owner, a shared machine token alone is never proof of ownership, and v1 cannot reconstruct the complete transactional session and relationship state guaranteed by v2. Current sync and status commands do not import or retire v1 transport data. Already-imported local legacy history can be purged in full (imports of any transport and any machine, plus historical import staging, incoming-cache directories, and receipts) with sase agent names purge-local-state.

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