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-cloud (Mutagent
Cloud). It is the default, so there is nothing to set up. You choose another
sandbox provider only when the platform has more than one configured.
How a run picks a sandbox provider
Without a flag, a run uses the default sandbox provider. To choose one, pass--sandbox-provider:
--preset <name> picks one; without
it, the default preset is used. See mutagent sandbox.
What a sandbox provider does not decide
A sandbox provider decides only where the sandbox runs. The rest of the run comes from other places:
Changing the sandbox provider does not change the model, the Environment or the agent.
Idle sandboxes
The same idle policy applies on every sandbox provider:- A sandbox stops after 15 minutes with no activity. A turn the agent is still working on counts as activity, for up to 4 hours.
- Before it stops, an interactive session is checkpointed.
- To continue, send the session a message. It wakes on a new sandbox from its last checkpoint and gets the message; the reference stays the same: