Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/omnigent-ai/omnigent/llms.txt

Use this file to discover all available pages before exploring further.

Cloud sandboxes let you run agent sessions in disposable cloud environments — no laptop required. Omnigent supports Modal and Daytona as sandbox providers. You can launch a sandbox manually from the CLI or configure the server to provision one automatically per session.
Cloud sandboxes run your model API keys inside the sandbox environment. Treat the sandbox environment as you would your laptop — don’t inject credentials you wouldn’t store on a machine you don’t fully control.

​
How managed hosts work

When the server is configured with a sandbox provider, it acts as a managed host: the server provisions a fresh sandbox for each new session automatically. Users start a session from the web UI or CLI and the sandbox appears as the host — no machine needs to stay online. You can also create and manage sandboxes manually from the CLI and register them as hosts yourself. Modal sandboxes live for at most 24 hours (a platform cap). They are ideal for short-lived or interactive coding sessions.
1

Install the Modal extra

pip install "omnigent[modal]"
2

Authenticate with Modal

modal token new
3

Create a sandbox

omnigent sandbox create --provider modal --server https://your-omnigent-server
The command provisions a new Modal sandbox, ships the Omnigent host into it, and prints the sandbox ID.
4

Register the sandbox as a host

omnigent sandbox connect --provider modal \
  --sandbox-id <sandbox_id> \
  --server https://your-omnigent-server
Modal sandboxes have a hard 24-hour lifetime set by the platform. When a sandbox expires, create a fresh one with omnigent sandbox create --provider modal.

​
Daytona sandboxes

Daytona sandboxes have no hard lifetime cap (idle auto-stop is disabled by the launcher).
1

Install the Daytona extra

pip install "omnigent[daytona]"
2

Set your API key

export DAYTONA_API_KEY=your-api-key
3

Create a sandbox

omnigent sandbox create --provider daytona --server https://your-omnigent-server
4

Register the sandbox as a host

omnigent sandbox connect --provider daytona \
  --sandbox-id <sandbox_id> \
  --server https://your-omnigent-server

​
Server-managed sandboxes

To have the server provision sandboxes automatically (one per session), add a sandbox block to your server config: Restart the server after updating the config. New sessions started from the web UI will automatically be assigned a managed sandbox host.

​
Listing and stopping sandboxes

For provider-side sandbox lifecycle management, use the provider’s own CLI: After you’re done with a sandbox, terminate it from the provider’s CLI to stop incurring costs. For a full guide to deploying Omnigent on various platforms — including Docker Compose, Render, Fly.io, and Modal — see the deployment overview.

Build docs developers (and LLMs) love

Get started for freeTalk to us