Runta Demos

Operating Rules

Prefer the CLI for a general demo. Use the Python or TypeScript SDK when the user asks for that language or the repo clearly uses that stack. If SDK details are needed, combine this workflow with $runta-python-sdk or $runta-typescript-sdk.

Check RUNTA_TOKEN before creating runtimes:

test -n "$RUNTA_TOKEN"

If the token is missing, stop before creating resources and tell the user to export RUNTA_TOKEN.

Use small resource sizes unless the demo needs more. Prefer names like demo, runta-demo, source-demo, restored-demo, or a user-requested name. Run runta ps -a first if there may already be resources with those names.

Do not delete runtimes, checkpoints, secrets, or secret rules unless the user asked for cleanup. Offer cleanup commands after demos that create resources.

Never print or store real secret values. For secret demos, use --value-env, --value-stdin, or --prompt.