Skip to main content
The cloud sandbox is a temporary execution environment managed by Flashduty: an isolated, ready-to-use container. The agent’s tool calls (running commands, reading and writing files, running Skills, connecting to MCP) all happen inside it, and you don’t install or maintain anything. When no self-hosted Runner is online and usable, sessions use the cloud sandbox by default. You can also pin a session to it manually. For the selection order and the per-session lock, see Environments.

Location and lifecycle

  • Location: the sandbox runs on the hosting provider’s serverless platform, in Hong Kong by default.
  • Idle pause: the sandbox pauses automatically when the session is idle and resumes on your next message, continuing in the same working directory.
  • Temporary: the sandbox is not a persistent machine. Don’t leave data in it that you need to keep.

Egress

The sandbox can reach any public address and cannot reach your private network: your VPC, dedicated lines, and the databases, APIs, and jump hosts behind them are unreachable. When an investigation needs to connect to those targets, use a self-hosted Runner on a machine that can reach your internal systems. The console’s network access option is “Allow all”, set in a cloud environment template.

Cloud sandbox vs. self-hosted Runner

Environments

Deploy and configure self-hosted Runners, and choose an environment in a session.

Console chat

See the environment and status bound to a session.