Early access. Cloud sessions and managed agent runs are not open to every account yet: we are
letting accounts in gradually while we test. They run in a cloud sandbox operated by Mutagent, so
there is nothing to host. A sandbox with nothing to do for 15 minutes stops; send the session a
message and it wakes up, delivers your message and carries on in the same conversation.
MUTAGENT_API_KEY=<key> mutagent login --json for a coding agent), and select a workspace with
mutagent workspaces use <workspace-name>.
mutagent sandbox providers
List the sandbox providers thatmutagent helix --sandbox-provider <name> accepts, and mark the
default.
--json, the command prints one object:
mutagent-cloud (shown as Mutagent Cloud in the web app) is the platform’s own sandbox provider
and the default for every run. A sandbox provider is where a sandbox runs. It is not an LLM provider (mutagent providers) and not
an Environment (mutagent env). A run that names a sandbox provider not in this list is refused
before anything starts, and the error lists the names you can use. See
Sandbox providers.
mutagent sandbox presets
List the presets thatmutagent helix --preset <name> accepts, and mark the default. A preset is a
named sandbox definition kept on the platform: what the sandbox runs, its CPU architecture, and the
sandbox provider it runs on.
--json, the command prints one object:
An unknown preset name is refused before anything starts.
In scripts
Read the list before you pass a name, so a run is not refused:If it fails
See CLI errors.
mutagent sandbox has other subcommands for running commands in a sandbox directly. Agent tasks use
mutagent helix. Run mutagent sandbox --help for the full list.