Skip to content

Configuration migration notes

This page collects user-facing configuration migrations. The configuration reference lists current keys, types, and defaults.

Machine identity

Machine identity belongs under id:

id:
  username: alice
  machine_name: athena

Top-level machine_name is accepted only as migration input. Run sase config init to move it under id and add or confirm id.username. The initializer preserves unrelated YAML and comments in the selected overlay. Run sase doctor to inspect identity issues.

Managed instruction templates

Use memory.h1_title instead of the unsupported amd_h1_title key. Template paths belong under memory.*; the top-level amd_agents_template, amd_agents_minimal_template, memory_sase_template, and memory_readme_template keys are accepted aliases, with the nested key winning when both are set.

File hook filters

Place hook matching fields under filters:

file_hooks:
  - name: research-highlights
    command: bob highlights create
    filters:
      path_globs: ["20*/**/*.md"]

The accepted fields are projects, sidecars, path_globs, agent_name_globs, ops, causes, and producers. Use path_globs; globs and top-level filter fields are ignored.

Repository configuration

repos.sidecar is a mapping with builtin and custom buckets. Each bucket maps a role name to its options; a list of entries with a name field is ignored. Run sase doctor to identify entries and place them in the right bucket. linked_repos and sibling_repos remain aliases for repos.linked; write new configuration with repos.linked.

SDD storage

Remove sdd.storage and sdd.version_controlled; they do not select storage. SASE chooses SDD storage from the workspace provider and repository configuration. Run sase doctor to find the unsupported keys. See SDD configuration behavior for the current storage layout.

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