Use InstaVM

InstaVM resource model

• Session is a short-lived execution sandbox.

• VM is a durable machine for longer-running work, SSH access, shares, or mounted volumes.

• Snapshot is a reusable machine image created from a VM or an OCI image.

• Share exposes a port from a session or VM.

• Volume is persistent storage mounted into a VM.

• Platform APIs include computer-use, audit, webhooks, API keys, and related control-plane features.

Preflight

Before any mutation:

• Ensure an API key is available.

• Probe the installed SDK surface before assuming helper names.

• If a native instavm CLI exists later, prefer it only when it is clearly the shortest path.

Load setup.md for exact install, auth, and surface-probe steps.

Routing

Load only the reference you need. Two references are usually enough, even for multi-step tasks.

Intent Reference Use for

Install, authenticate, choose session vs VM, create or delete compute setup.md SDK install, API key handling, session basics, VM CRUD, context checks

Run code, transfer files, snapshot, clone, or build from OCI compute.md execution, uploads/downloads, async jobs, VM snapshots, OCI snapshots

Connect to a machine or expose it to the network access.md SSH keys, ssh instavm.dev , shares, egress, custom domains

Persist or move data storage.md volumes, checkpoints, mounts, file operations

Use advanced control-plane APIs or fall back to raw HTTP platform.md computer-use, browser, API keys, audit, webhooks, REST/OpenAPI fallback

Prefer or inspect a future native CLI cli.md CLI discovery, command help, when to choose CLI over SDK

Execution rules

• Prefer the installed SDK surface over docs, tests, or memory.

• Use a session for short-lived execution. Use a VM for SSH, shares, or mounted volumes.

• Keep egress narrow and shares private unless the user explicitly wants broader access.

• Confirm destructive actions and read back the result after mutation.

• If the installed SDK lacks the needed helper, use raw HTTP only after checking the latest schema.

Composition patterns

• Bootstrap a working VM: setup -> compute -> access

• Create a reusable base image: setup -> compute

• Create a persistent worker: setup -> storage -> access

• Handle an SDK gap: relevant operational reference -> platform

• Add future CLI support: cli -> relevant operational reference

Response format

For operational responses, return:

• What was done and where.

• The result: IDs, URLs, status, or key output.

• What to do next, or confirmation that the task is complete.