Providers and models

A provider is the coding-agent CLI that runs the model behind an agent turn.

The idea in one picture

Task and workspace ──► SASE ──► Provider CLI ──► Model
                         ▲
                    size alias

The diagram shows SASE routing a task to a provider and model, which a size alias can help select.

How it works

SASE starts supported provider CLIs through a common agent workflow. The provider connects the task to a model and its own authentication system; SASE keeps track of the work around that invocation.

You can select a provider and model directly, or use a size alias such as @large when a prompt needs a general capability level rather than a specific model name. SASE resolves the alias to an available provider and model, so reusable prompts can describe the work without being tied to one vendor's catalog.

When it matters

• Use a size alias when a task should stay portable across provider choices.
• Choose a provider and model directly when the task depends on a particular capability or account.
• Check provider readiness before launching work that depends on its CLI.

Do it

• Choose providers and models — ready one provider and pick the model agents use.
• Get started with SASE — check provider readiness and launch a first agent.

Look it up

• Agent providers — install and authenticate supported providers.
• Providers and models — model selection and provider behavior.
• Glossary — provider and model terms.
• Design decisions — how size aliases route work across providers.

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