Skip to content

Display and reading configuration

Configuration for Markdown rendering, paging, and reading surfaces.

markdown

The column width SASE wraps generated Markdown prose at. It governs every Markdown surface SASE writes or renders itself: plan files, bead notes and pages, memory shims and the generated AGENTS.md/provider instruction files, generated skills, prompt archives, SDD documents, and the default --wrap for sase bead show and sase plan show. The value is resolved on each call, so an edit takes effect on the next command without restarting anything.

Values below the minimum, of the wrong type, or in a malformed config fall back to the shipped default rather than raising: a broken sase.yml must never turn sase plan propose into a traceback.

markdown:
  print_width: 88

Generated reference for markdown

The minimum of 20 is the floor below which SASE's display wrapper stops wrapping entirely, so a smaller value would silently do nothing.

Sharp edge: the prettier CLI cannot read this field. prettier (via just fmt-md, CI, or an editor integration) discovers its configuration from files on disk — a repo's package.json, .prettierrc, and friends — and those declarations mirror SASE's shipped default, not your effective configured value, so that a stock checkout is self-consistent for a contributor with no SASE config at all. If you configure a non-default markdown.print_width and then run sase init inside a repo whose prettier config still declares the default, the regenerated AGENTS.md will be wrapped at your width and that repo's fmt-md-check will fail on it. Change the repo's prettier config to match, or leave the field at its default.

pager

File-aware syntax highlighting for the SASE pager. Eligible raw sources — files, Markdown documents, diffs, and stdin with a convincing diff prefix — receive a muted language-aware overlay after first paint. Formatted cards, bead detail, commit manifests, and producer-styled ANSI stay unhighlighted.

pager:
  syntax: auto

Generated reference for pager

CLI --syntax overrides this field. --syntax none and --color never disable the added layer for the rest of the session, including followed targets. Unknown values fail schema validation (sase config / doctor diagnostics) and the runtime accessor falls back to auto so a hand-edited sase.yml cannot crash the pager.

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