For the complete documentation index, see llms.txt. This page is also available as Markdown.
Benchmarked

Archil

Archil provider for ComputeSDK

Installation & Setup

Add your Archil credentials to a .env file:

Usage

Archil is exec-only — create() resolves a handle to an existing Archil disk id. Each command runs in an Archil-managed container with that disk attached.

Configuration Options

Supported Operations

Method
Supported
Notes

create

Resolves an existing disk from top-level diskId.

getById

Requires the disk id.

list

Lists all disks visible to the API key.

destroy

no-op

Disk lifecycle is managed by Archil.

runCommand

Calls Archil's HTTP exec endpoint and waits for completion.

getInfo

getUrl

Each exec runs in a fresh ephemeral container — no port to expose.

filesystem

Accepts normal paths and maps them into /mnt/archil; shared-mode checkout/checkin is automatic.

Limitations

  • Each exec call provisions a fresh container — no persistent state between calls beyond what is written to the disk.

  • Responses are truncated to ~5 MB by the Archil control plane.

  • getUrl is not supported — each exec runs in a fresh ephemeral container, so there is no long-lived process to expose a port on.

  • Filesystem operations accept normal absolute paths and map them into /mnt/archil internally.

  • Raw runCommand strings are not rewritten. Commands that access the disk directly must use /mnt/archil themselves.

Last updated

Was this helpful?