> ## 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. Deploying is the default path: reactor init scaffolds a workspace, reactor auth login authenticates, and reactor model deploy registers the model, publishes the release with the weights/ folder, and activates it on Reactor's GPUs, in one command from that workspace. Docker must be running, because the publish step builds the image locally. Bump model.version in reactor.yaml before redeploying a change, because a release that already has an image is reactivated as it is. Deployment access is granted per account, so contact team@reactor.inc if a deploy is refused. Every key in reactor.yaml is documented at /deploy/platform/reactor-yaml. Model code imports reactor_runtime; Python client code imports reactor_sdk. The runtime overview explains the model interface. Running the model on your own machine with reactor run is optional and needs a GPU you attach with --gpus; /deploy/development/local-testing covers that loop and pairs a complete brightness model with a Python client test in a separate brightness-test workspace.
> Reactor hosts multiple models, each with its own connect slug (modelName) and command/event schema. The video model catalog — slug, typed SDK package, and links to its schema — is at /model-api-reference/overview. Robotics policy documentation starts at /robotics/overview; X-WAM observations, actions, and client integration are under /robotics/xwam/; Cosmos3 Nano Policy DROID is under /robotics/cosmos/nano-policy-droid/. 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.

# Cosmos3 Nano Policy troubleshooting

> Diagnose missing action chunks, step acknowledgements, and observation mapping.

| Symptom | Check |
| - | - |
| Connection rejected or no capacity | Use `https://api.reactor.inc`, the correct model identifier, and an authorized key. Capacity errors can occur before inference; retry with backoff or contact Reactor. |
| No first chunk | Wait for `READY` before publishing. All three named tracks must deliver frames, and `proprio_json` must parse as row lists. |
| No next chunk | Acknowledge the last received `step` after execution. Repeating or lowering the acknowledged counter does not open the gate. |
| State ignored | Encode JSON as a string inside the named command payload. Check the 8,000-character limits and row widths. |
| Correct shape, wrong motion | Check camera identities, joint ordering/units, and absolute-target interpretation. Tensor shape does not prove embodiment compatibility. |
| Gripper moves the wrong way | DROID uses `0` open and `1` closed. Convert your driver's units/polarity explicitly. |
| Values differ on identical inputs | Sampling is unseeded and video transport can change the received pixels; exact numerical equality is not a supported check. |
| Unexpected step after reset | Reset restarts the counter but preserves input fields. Use a new session when old acknowledgements or replies could be mistaken for new ones. |

## Reference-client behavior

Keep the event loop responsive so camera publishing and message handling can continue. Start a fresh
session after an uncertain timeout; do not fabricate an acknowledgement to force progress. The
documented endpoint supports reset as specified in the
[reference](/robotics/cosmos/nano-policy-droid/reference#task-changes-and-reset).

## Report a problem

Include the model identifier, SDK/client versions, session ID, timestamps, track names/shapes,
proprioception dimensions, last received and acknowledged counters, and exact error text. Never
include an API key. State whether the failure occurred during connection, first prediction, or
subsequent control steps.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.