using-medusa-cloudlisted

# Managing Medusa Cloud Resources Operational guide for AI agents managing Medusa Cloud infrastructure through the `mcloud` CLI. Covers setup, deployments, debugging, environments, and variables. ## Constraints - **Always pass `--json`** when parsing CLI output. Plaintext output is for humans and may change without warning. - **Confirm context before mutating.** Run `mcloud whoami --json` before any state change. - **Read before you write.** Run a `get` or `list` before any `delete`, `redeploy`, or `trigger-build`. - **Use `--yes` for destructive operations.** `delete` commands (including `variables delete`) require `--yes` in non-interactive mode. - **Variable changes need a deploy to apply.** `variables set`/`delete` don't rebuild or redeploy: `redeploy` for runtime changes, `trigger-build` for build changes. - **Production environments cannot be deleted.** `mcloud environments delete` errors on production by design. - **Never pass `--reveal` unless the user explicitly asks.** Secret values appear in terminal scrollback and logs. - **`--json` and `--follow` are incompatible.** Use bounded time windows (`--from`/`--to`) with `--json` for programmatic log ingestion. ## CRITICAL: Load Reference Files When Needed **Load these references based on what you're doing:** - **Setting up the CLI?** → MUST load `setup.md` first - **Debugging a failed deployment?** → MUST load `debugging-deployments.md` first - **Managing environments or variables?** → MUST load `environments-and-