Skip to main content
All interfaces start from an image and create operations. Choose based on how the caller needs to submit, observe, and control work.

Capability map

The examples and method names on this page use Python SDK 0.3.6 and CLI 0.9.4. For MCP, check the tools exposed by the server connected to your client.

Interface boundaries

  • A Python SDK 0.3.6 run() call prepares work; awaiting the returned object submits it and waits for the final result.
  • A CLI session tracks a selected image and local workflow history. It does not keep a VM alive.
  • REST is the reference for operation status, SSE events, and additional subprocesses.
  • MCP capabilities depend on the tools exposed by the deployed server. Check the connected server before building a workflow around a specific tool.
Choose persistence before submission on every interface. See Images, checkpoints, and branches for defaults and result-image outcomes.

Continue