> ## 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
> 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.

# reactor model status

> Show model release status

```sh theme={"theme":{"light":"github-light","dark":"github-dark-high-contrast"}}
reactor model status [<name>|<name>:<release>] [flags]
```

## Description

Show status for a model or a specific model release.

**With \<name>:\<release>, the report covers three facets:**

* Release:  whether the release tag is registered and currently deployed
* Image:    whether a container image has been pushed via `reactor model publish`
* Weights:  whether weights have been uploaded via `reactor weights upload`

With \<name> only, the report shows the model metadata and all registered
releases, including deployment, image, and weights rollups.

Pass `-l` for a per-region instance table (DESIRED/RUNNING/HEALTHY/IDLE) of the
model's live fleet. The table header names the currently-deployed release; the
counts are not filtered by release. HEALTHY counts pods with a live runtime
heartbeat (idle or serving), which is the signal a readiness probe cannot give
for single-session model pods. A cell reads "?" when the server did not report
that count. "Instances: none" means no cluster reported live instances: the
model may have no deployed release, the rollout may not have landed yet, or
every Supervisor serving it failed to report.

Use `-o` json|yaml for the same per-region data in a structured document. It
names one release (the deployed one, or the newest when none is deployed) and
reports instances as \[] for an empty fleet, or null with instances\_unavailable
when the lookup failed. Both flags apply to the \<name> form only.

With no argument, the model name is inferred by walking up from the current
directory to the nearest enclosing reactor.yaml (stopping at the repository root).

**Examples:**

```sh theme={"theme":{"light":"github-light","dark":"github-dark-high-contrast"}}
reactor model status
reactor model status my-model
reactor model status my-model -l
reactor model status my-model -o json
reactor model status my-model:v1.0.0
reactor model status my-model:v1.0.0-gabc1234
```

## Options

| Flag                  | Description                                                                |
| --------------------- | -------------------------------------------------------------------------- |
| `-l, --long`          | Long format: append a per-region instance table for the model's live fleet |
| `-o, --output string` | Output format: table, json, yaml (default "table")                         |

## Global options

| Flag              | Description                                                                           |
| ----------------- | ------------------------------------------------------------------------------------- |
| `--server string` | Reactor API server URL (default "[https://api.reactor.inc](https://api.reactor.inc)") |
| `-v, --verbose`   | Enable verbose output                                                                 |

## See also

* [reactor model](/deploy/cli-reference/reactor_model) - Model management commands