Skip to content
GroundboxDocs
API referenceStatusPricing
DashboardStart free
GroundboxGitHub Actions runners and Linux sandboxes for AI agents. One key, one bill.System status

Product

CI runnersSandboxesBuilds and cacheAgent computersPricing

Developers

DocsAPI referenceAPI explorerCLIMCP serverBenchmark

Compare

vs GitHub-hostedvs Blacksmithvs E2Bvs DaytonaAll comparisons

Company

Talk to usSupportcontact@groundbox.devGroundmail ↗
© 2026 Groundbox
TermsPrivacyllms.txt
OverviewCI in one lineFirst sandboxHand it to your agent
Sizes and labelsCachesBuild cachesMigrateci waitTerminal on a jobPublic repositoriesAuto sizeAuto size: own runnersFlexCI tune-upSplit tests by timeDocker buildsGitLab CI
Start, exec, filesFrom a Docker imageCommandsForkTime machineSnapshotsPause and resumeStop and startIdle pause and wakeScheduled runsPreviewsSecretsEgress allowlistFlex sandboxesTemplatesVolumes
Push and pullIn GitHub ActionsStorage and retention
Desktop and actionsLive view in your appHuman handoffSign in onceAgent loop example
BucketsAccess keysMount a bucket
Move from Runloop
Omnara
REST APIAPI explorerOpenAPI referenceCLIMCP serverSDKsKeys and capsLeave or delete a team
  1. Integrations
  2. Omnara
Markdown
Open in
ClaudeChatGPT
On this page

    Run Omnara machines on Groundbox

    Omnara runs coding agents on machines from a pool you connect. With a Groundbox pool, each machine is its own Groundbox sandbox: a Firecracker microVM with Ubuntu 24.04, Git, Node.js, Python, Go and Docker, started in about a second, paused with its memory when idle, and billed by the second. Omnara's Groundbox page lists every pool field; this page covers the Groundbox side.

    Set it up

    1. Make an API key. On Keys, create a key with the sandboxes:read and sandboxes:write scopes. Give it a monthly spend cap if you want one. Machines run and bill in that key's team.
    2. Add a card. Until a team has a card on file, each sandbox ends after an hour, so Omnara's long-lived machines are refused. Add one under Billing; the free credit is still used first.
    3. Store the key in Omnara as an org-owned secret.
    4. Create the pool. On Omnara's Machines page, click New pool, choose Groundbox, and pick the secret, a template (or none), the machine size and the limits.

    Your tools in a template

    Leave the template empty to use your team's default template, or Groundbox's own image when the team has none. It already has everything Omnara's daemon needs. To add your own tools, build a template once:

    Terminal
    curl -X POST https://api.groundbox.dev/v1/templates \
      -H "Authorization: Bearer $GROUNDBOX_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "name": "omnara-machine",
        "apt": ["ripgrep", "postgresql-client"],
        "npm": ["pnpm"],
        "cpus": 2,
        "memory_gb": 4
      }'

    Give the template the same CPU and memory as the pool's machines. A machine of the template's size starts from its warm snapshot; any other size boots cold.

    Sleep when idle

    Set sleep_after_ms on the pool (through Omnara's API for now) and an idle machine pauses with its memory, files and running processes. It resumes in about a second when an agent needs it, and a paused machine pays only for its disk.

    JSON
    {
      "name": "groundbox-pool",
      "provider": "groundbox",
      "provider_auth_secret_id": "sec_...",
      "default_machine_provider_options": {
        "template": "omnara-machine",
        "sleep_after_ms": 300000
      },
      "default_machine_cpu": 2,
      "default_machine_memory_mb": 4096
    }

    Sizes and price

    • 1 to 16 vCPU per machine, with memory in whole GB, up to 4 GB per vCPU, included in the price.
    • $0.04 per vCPU-hour while running, billed by the second.

    Limits

    • A team keeps up to 10 paused sandboxes unless its plan says otherwise. At that limit, an idle machine stays running instead of sleeping.
    • A machine that runs a month without sleeping is ended, and one that sleeps a month is deleted. Keep setup in a template.
    • Omnara's daemon token lives in the machine's environment. Groundbox can limit which hosts a sandbox reaches with egress rules, but does not inject headers into outbound traffic.

    More on providers in Omnara's providers overview. Questions: support.

    ← PreviousMove from RunloopNext →REST API
    System statusSupportPricingllms.txtgroundbox.dev