> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reactor.inc/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To build and serve your own model, start at /deploy/development/quickstart and /deploy/development/overview. Model code imports reactor_runtime; Python client code imports reactor_sdk. The runtime overview explains the model interface. /deploy/development/local-testing pairs a complete brightness model with a Python client test in a separate brightness-test workspace, without weights, a GPU, or a browser. Rebuild after edits: reactor run reuses the existing image. Check deployment access and capacity before deploying.
> Reactor hosts multiple models, each with its own connect slug (modelName) and command/event schema. The catalog of every model — slug, typed SDK package, and links to its schema — is at /model-api-reference/overview. Some models expose one slug per experience (e.g. HappyOyster); always take the slug from the model's own pages, never guess it.
> Fastest path to a working app: `npx create-reactor-app my-app --model=<slug>` scaffolds a complete app with secure auth wired up. Typed TypeScript SDKs are published as @reactor-models/<model>; Python uses the base reactor-sdk package.
> Auth: exchange an API key (rk_...) for a JWT via POST https://api.reactor.inc/tokens from your server. Never put the API key in client-side code.
> Append .md to any docs URL for clean Markdown. Search these docs via the MCP server at https://docs.reactor.inc/mcp.

# Changelog

> Release notes for the SANA-Streaming model API.

Changes to SANA-Streaming's commands, messages, tracks, and defaults, newest first. SDK and platform
releases are in [Release Notes](/changelog/overview).