use-instavm

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

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.

Before any mutation:

For live deploy, host, create, update, snapshot, or delete requests, verify authentication first.
If no API key or authenticated CLI path is available, stop and ask for credentials. Do not spend time generating deploy scripts, repo changes, or long offline setup unless the user explicitly asks for offline preparation.
After auth is confirmed, 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

references/setup.md

for exact install, auth, and surface-probe steps.

在执行任何变更操作前：

加载

references/setup.md

获取确切的安装、认证和接口探测步骤。

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

```
references/setup.md
```
: install, auth, choose session vs VM, create or delete compute.
```
references/hosting.md
```
: host or deploy an app, including static sites, simple web apps, long-lived servers, shares, and deploy verification.
```
references/compute.md
```
: run code, transfer files, snapshot, clone, or build from OCI.
```
references/access.md
```
: connect to a machine or expose it to the network.
```
references/storage.md
```
: persist or move data with volumes, checkpoints, and mounts.
```
references/platform.md
```
: advanced APIs and REST fallback.
```
references/cli.md
```
: prefer or inspect a future native CLI.

仅加载所需的参考文档。即使是多步骤任务，通常两个参考文档就足够。

Trust the live product surface over skill text: start with the installed SDK, actual CLI help if a CLI exists, and read-back state from the API after mutations.
Detect capability before use. For SDK, inspect attributes or method signatures. For CLI, use
```
--help
```
only if the binary exists. Fetch the latest OpenAPI or live docs only when capability is unclear, a field may be unsupported, or you need a REST fallback.
Use a session for short-lived execution. Use a VM for SSH, shares, mounted volumes, or user-facing hosting.
Keep egress narrow and shares private unless the user explicitly wants broader access.
For live infrastructure requests, a quick repo inspection is fine, but do not do multi-minute offline scaffolding before auth is confirmed.
After mutation, read the resource back. If a field is ignored or missing in the follow-up state, treat that capability as unsupported in the current environment.
If the installed SDK lacks the needed helper, use raw HTTP only after checking the latest schema.

优先信任实时产品接口而非技能文本：从已安装的SDK开始，如果存在CLI则查看实际的CLI帮助，变更操作后从API读取返回状态。
使用前先检测功能。对于SDK，检查属性或方法签名；对于CLI，仅当二进制文件存在时使用
```
--help
```
。仅当功能不明确、字段可能不支持或需要REST降级方案时，才获取最新的OpenAPI或实时文档。
短期执行任务使用Session。SSH访问、共享、挂载卷或面向用户的托管使用VM。
除非用户明确要求更广泛的访问权限，否则保持出口规则严格、共享私有。
对于实时基础设施请求，快速检查仓库即可，但在确认认证前不要进行耗时数分钟的离线脚手架搭建。
变更操作后，读取资源的返回状态。如果后续状态中某个字段被忽略或缺失，则认为当前环境不支持该功能。
如果已安装的SDK缺少所需的辅助工具，在检查最新的Schema后再使用原始HTTP请求。

For operational responses, return:

对于操作类响应，返回以下内容：