Providers and models

Use these pages to look up how SASE connects provider CLIs and routes model requests.

This document describes the LLM provider abstraction layer in sase. The system supports pluggable LLM backends (Claude Code, Codex, Antigravity CLI (agy), Qwen Code, OpenCode, Meta's Muse Code, and xAI's Grok Build are bundled; additional providers can ship as external plugins) behind a shared orchestration layer that handles preprocessing, invocation, and postprocessing.

This page documents how SASE integrates each provider. To install and authenticate a provider CLI in the first place, see Installing & Authenticating Agent Providers.

Provider CLIs

• Agent CLIs — install, authenticate, and inspect supported tools.
• Claude Code · Antigravity · Codex · Qwen · OpenCode · Muse Code · Grok Build
• External provider plugins — extend the provider registry.

Models and routing

• Models and aliases — model catalog, tiers, effort, and role aliases.
• Provider routing — temporary overrides, disables, and priority.
• Provider configuration — shared settings and CLI options.
• Provider usage — subscription capacity and usage-limit behavior.
• Retry and fallback — provider failures and recovery.

Related

• Environment variables — provider and runtime variables.

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