Integrations
Use smol machines from tools you already run. Each integration below starts ordinary smol machines, through the smolmachines SDK, the smolvm CLI or the Cloud API: each one its own Linux guest, with branching where the integration uses it.
Most of these live in another project’s repository. The Code column says where, and that project’s issue tracker is the place to report problems with the integration itself.
Testing
| Integration | What it does | Code | Runs on |
|---|---|---|---|
| Crabbox by OpenClaw | --provider smolvm runs Crabbox’s warm-a-box, sync-the-diff, run-the-suite loop in a smol cloud machine, with the working tree uploaded through the files API. Needs a smol cloud API key in SMOLMACHINES_API_KEY | internal/providers/smolvm, in Crabbox’s repository | smol cloud |
| e2e | Runs each web test attempt in its own branch of a warm Chromium machine, signed in once by prepare | @e2e-dev/smol, in the e2e repository, written by smol machines | Local engine |
Agent evaluation and RL
| Integration | What it does | Code | Runs on |
|---|---|---|---|
| Harbor | Runs each trial in a machine branched from one warm machine per task environment. Install harbor[smol] and pass -e smol | environments/smol.py, built into Harbor, written by smol machines | Local engine or smol cloud |
| AgentEnv Framework by Scale AI | A sandbox provider that runs AgentEnv agents and environments in local machines | smol_vm, in Scale AI’s repository, written by smol machines | Local engine |
| NeMo Gym | A sandbox provider: install smolmachines[nemo-gym] and select smol in NeMo Gym’s sandbox configuration. An image mapped in checkpoints branches a prepared, running machine | smol.nemo_gym, in the smol Python SDK | Local engine or smol cloud |
| verifiers by Prime Intellect | smol.verifiers.SmolRuntime, a runtime where each rollout runs in its own machine, or in a branch of a running machine. It works with verifiers 0.2.x: install smolmachines[verifiers] and verifiers<0.3, and set target="local" for the local engine (the default is smol cloud) | smol.verifiers, in the smol Python SDK | Local engine or smol cloud |
Agents and orchestration
| Integration | What it does | Code | Runs on |
|---|---|---|---|
| Amika by Fixpoint | amika-hostd makes a computer you own an Amika host: it starts smolvm serve and runs each Amika rig there as a local machine. Needs an Amika account | js/amika-hostd and the smol provider, in Fixpoint’s amika repository, written by Fixpoint | Local engine |
| exo | Runs an exo agent’s sandbox as a microVM. smolvm is exo’s default sandbox, so no flag is needed, and --sandbox smolvm picks it explicitly | sandbox_provider/smolvm, in exo’s repository, first written by smol machines and now maintained by exo | Local engine |
| Hermes Agent by Nous Research | A terminal backend that runs Hermes’s terminal, file and code tools in a local machine. Install it from Hermes’s plugin catalog with hermes plugins install smolmachines | hermes-smolmachines, a community plugin in Hermes’s plugin catalog, written by smol machines | Local engine |
| Pydantic AI Harness by Pydantic | SmolSandbox, a capability that runs a Pydantic AI agent’s shell and file tools in a persistent local machine. Install pydantic-ai-harness[smol] | smol_sandbox, built into Pydantic AI Harness, written by Pydantic | Local engine |
| Ray Sandboxes | A backend for ray.experimental.sandbox, with live branching of a running sandbox. Install smolmachines[ray] and call ray.init(runtime_env=ray_sandbox.use_smol()) | smol.ray_sandbox, in the smol Python SDK | Local engine or smol cloud |
| Sandbox orchestration harness by the Temporal community | A smol cloud compute provider, with checkpoints and restores | sdk/compute/smolcloud, in the harness repository, written by smol machines | smol cloud |
| sweeper by The Paper Compute Company | --vm-backend smol runs sweeper’s Claude Code lint-fixing agents in one machine per run, with the Anthropic key bound as a credential the guest cannot read | pkg/vm/smol.go, in The Paper Compute Company’s sweeper repository, written by The Paper Compute Company | Local engine |
Ray’s sandbox API is experimental in Ray itself, so its shape can change between Ray releases.
Agent tools
| Integration | What it does | Code | Runs on |
|---|---|---|---|
| MCP server | npx -y smolmachines-mcp gives any MCP client tools to create a machine with a project copied in, run commands, branch, checkpoint, restore and export | sdk/mcp, in the smol repository | Local engine, or smol cloud with SMOL_CLOUD_TOKEN |
Tool marketplaces
Monid does not run in your project. It sells smol cloud machines to agents as one of its tools: an agent uses them with its Monid key and pays from its Monid balance.
| Integration | What it does | Code | Runs on |
|---|---|---|---|
| Monid | The smolmachine tool: an agent creates smol cloud machines, runs commands in them, moves files in and out, and stops, starts and deletes them through Monid. The calls are free, and each machine is metered while it exists and paid from the agent’s Monid balance | Built into Monid’s tool catalog, written by Monid | smol cloud |
Sign-in
AgentID does not start machines. It is a way for an agent to sign in to smol cloud with an account of its own.
| Integration | What it does | Code | Runs on |
|---|---|---|---|
| AgentID by AgentMail | An agent signs in to smol cloud with its own AgentMail inbox, through OpenID Connect, into an account of its own or as a member of your organization | Built into the smol cloud sign-in page | smol cloud |
Add an integration
To propose an integration or report one that is missing from this page, open an issue on smol-machines/docs.