Agent operating guide

Use this page when an AI agent, coding assistant, CI worker, or operator needs to build and release software through MIOSA. The CLI is the authoritative happy path - prefer its --json output over reconstructing lower-level API calls.

1. Discover the current inventory

miosa catalog --json
miosa deploy list --json
miosa deploy get <deployment> --json

catalog reports the canonical compute products, templates, sizes, and readiness the platform offers right now. deploy list and deploy get return the deployments you already own. Do not guess a resource id from an old transcript when these commands can return the current inventory.

2. Develop in a persistent sandbox

miosa create my-dev-box --template nextjs --wait
miosa console my-dev-box --cwd /workspace
miosa doctor
miosa preview create my-dev-box 3000 --name candidate

create provisions the sandbox and, with --wait, blocks until it is ready. console opens an interactive shell and resumes the same machine on a later run. doctor checks configuration, connectivity and authentication. Preview publishes a port at a public URL and never promotes production.

3. Publish the exact release

A candidate is not production merely because its build succeeded. Promotion targets one exact immutable release, and the production URL stays stable while the active release changes.

Pick what you need

Next