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

# Check release status

> See at a glance whether a release is registered, pushed, and uploaded.

`reactor model status` reports the deployment, image, and weights state of your releases. The
argument shape picks between two display modes: a model overview and a per-release report.

## Usage

Run it from your workspace with no argument to print the **model overview**: model metadata plus a
rollup row for every registered release.

```sh theme={"theme":{"light":"github-light","dark":"github-dark-high-contrast"}}
reactor model status
```

Pass `<model>` to see the same overview for a different model, or `<model>:<release>` for the
detailed per-release report:

```sh theme={"theme":{"light":"github-light","dark":"github-dark-high-contrast"}}
reactor model status my-awesome-model            # model overview
reactor model status my-awesome-model:v1.0.0     # release detail
```

### Long format and structured output

Pass `-l` to append a per-region table of the model's live instances, with desired, running,
healthy, and idle counts. `-o json` and `-o yaml` return the same data as a structured document.
Both flags apply to the `<model>` form only.

```sh theme={"theme":{"light":"github-light","dark":"github-dark-high-contrast"}}
reactor model status my-awesome-model -l         # add the per-region instance table
reactor model status my-awesome-model -o json    # the same data, structured
```

## Example output

```
Model:    my-awesome-model:v1.0.0
Release:  ○ registered (created 3m0s ago, never deployed)
Image:    ✓ pushed (1m30s ago)
Weights:  ✗ not uploaded (run `reactor weights upload`)
```

## Status glyphs

| Glyph | Meaning                                                                       |
| ----- | ----------------------------------------------------------------------------- |
| `○`   | Release is registered but not yet deployed                                    |
| `✓`   | This component is in place (image pushed, weights uploaded, release deployed) |
| `⊘`   | Previously deployed; a newer release has since been deployed                  |
| `✗`   | Missing; the line includes a hint pointing at the command to run              |

When a component is missing, the status line points directly at the next step:

* `Image: ✗ not pushed` runs [`reactor model publish`](/deploy/platform/publish).
* `Weights: ✗ not uploaded` runs [`reactor weights upload`](/deploy/platform/publish#weights).
* `Release: ○ registered (never deployed)` runs [`reactor model deploy`](/deploy/platform/deploy).

## See what's actually running

`status` shows which release is deployed;
[`reactor model instances`](/deploy/platform/manage#list-running-instances) shows which **instances** are
currently serving it. Pair them when triaging "the release is marked deployed but clients aren't
connecting":

```sh theme={"theme":{"light":"github-light","dark":"github-dark-high-contrast"}}
reactor model status        # is this release the active one?
reactor model instances     # are any instances running, and are they healthy?
```

## Next

<CardGroup cols={2}>
  <Card title="Deploy a release" icon="rocket" href="/deploy/platform/deploy">
    Activate a release once its image and weights are in place.
  </Card>

  <Card title="Manage the model" icon="sliders" href="/deploy/platform/manage">
    Update the spec, list running instances, or delete the model.
  </Card>
</CardGroup>