Skip to main content
Fly Machines and Fly Sprites are independent providers. Use fly-machines here: each Session owns a dedicated App, private network, and Machine. The durable resource ID is the App ID. An App created before a lost Machine response must still be retained and reconciled.

Configuration and permissions

Use a Token authorized for the target organization, App/Machine creation/deletion, and private proxy access. Access to an unrelated App alone is insufficient. The control-plane host also needs fly on PATH and functioning private transport. Listing validation does not prove that transport works. Machines currently use shared CPU with 2 vCPU; undefined config fields cannot override it. Configuration does not accept an existing App name, avoiding accidental ownership of shared resources. These examples use local management clients; see self-hosting for hosted initialization. The private key stays in the control plane. Retain the created connection ID rather than recreating it.
Validation only lists organization Apps. Explicitly enable after ready validation; revalidate/enable after configuration or key changes. Existing Sessions remain pinned.

Built-in and public OCI execution

Built-in Harnesses use node:24-bookworm. Follow the first Session with connection.id and a compatible model/Harness, verifying execution and artifacts. For public OCI, follow image registration and pin a digest. An OpenCode image in current scoped records is: ghcr.io/anomalyco/opencode@sha256:763ea3bce6bdaee6d6092775c83c03a90b11b2a74dcfb89942a4cb82a99f974e Use matching opencode-v1 protocol/command and inspect exact combination records for models, SDKs, and scenarios. Registration is not a fresh execution pass. Independently verify both SDKs, task, files, required Tools, and cleanup. Private images are unsupported; registry credentials are rejected. The VM may install Python, Bash, timeout, and other prerequisites using Alpine/Debian-family package managers. Unsupported preparation fails. Commands execute as root; image USER is not a verified isolation boundary. The source digest does not describe an unchanged prepared filesystem. The default image entrypoint is not automatically run; Runtime launches the registered command.

Private access and limits

No public services are configured; existing App secrets or volumes are not inherited. Each App has its own private network. The control plane launches fly proxy on loopback to reach the specific Machine privately. Browsers use Hexagon preview authorization, never account Tokens or raw provider URLs. A listening local proxy does not establish WireGuard, DNS, or guest readiness. Diagnose each layer. The connector does not declare network_allowlist; choose another provider when domain restrictions are required. File reads are capped at 64 MiB with chunk checks; higher layers may impose smaller limits. Foreground commands allow at most 590 seconds and background commands 3600 seconds. These are not total Run duration limits.

suspend/start and cold boot

Idle uses suspend; the next submit starts the Machine automatically. Fly can cold-boot without a usable memory snapshot, so the dependable boundary is filesystem state rather than process memory. Check Runtime, conversation, and preview services separately; arbitrary background processes are not guaranteed to continue. Restore selects the currently unique Machine in the owned App, acquires its lease, and rereads its state to fence stale requests. It accepts started or suspended, rejects stopped or multiple Machines, and does not create replacement compute. This step alone does not compare against a separately persisted original Machine ID. Command execution additionally requires the Machine operation metadata to match the App operation. Empty/ambiguous means the App exists with an unexpected resource structure requiring investigation. Do not manually replace its Machine. Use idle and wake to verify two-turn files/conversation with exact image/model records. Do not manually replace compute to hide recovery failures.

Read resource observations separately

The November 18 MiniMax matrix records public OCI tasks on Fly Machines, including pinned OpenCode combinations. Its scope is native continuation, remote Tool, environment, artifacts and cleanup through both SDKs; it does not certify a fresh Web/preview or idle journey for each cell. Use the exact image/protocol/model entry in the linked combination records, rather than treating the image name as a compatibility guarantee.

Cleanup and reconciliation

Close releases local proxies, deletes the Session-owned App, and confirms App absence. This applies only to that dedicated resource group, not every App in the organization. Do not add unrelated resources to it or reuse this deletion flow on shared Apps. Partial creation can leave an empty App; absent compute does not establish App cleanup. Transport failure is not absence; explicit provider 404 is. Preserve original App/operation IDs and reconcile without blindly creating another App after uncertainty. For fly_machine_not_ready, inspect unique Machine/state/ownership. For fly_resume_state_pending, inspect the original state. For harness_runtime_prerequisites_unavailable, inspect image preparation. For fly_app_deletion_unconfirmed, inspect original App deletion. This page is source-reviewed without new cloud execution. Historical scope is in the execution matrix and serverless ledger. Sources: image lifecycle, connector, private proxy. Next: OCI Harness, idle and wake, reconciliation.