Skip to main content
Modal is a remote environment provider for task images that can run in cloud sandboxes. It is a good fit for SWE-bench and Terminal-Bench style workloads where the task metadata already identifies a compatible registry image.

First-Time Setup

  1. Create a Modal account from the official signup page.
  2. Configure Modal credentials for the machine that runs AgentCompass.
  3. Export MODAL_TOKEN_ID and MODAL_TOKEN_SECRET, or let the Modal CLI write credentials to ~/.modal.toml.
  4. Run a single AgentCompass task before increasing concurrency.
For local development, the Modal CLI setup flow is usually enough:
For automated runners or shared workspaces, create a service user token in Modal and export it in the shell or CI secret store:
AgentCompass authentication precedence is:
Do not commit Modal tokens to config/defaults.yaml. Use environment variables or a private config file passed with --config.

Verify Credentials

Use the Modal CLI to verify the active credentials:
Then run one recipe-backed task with AgentCompass:

SWE-bench Verified

The SWE-bench Modal recipe selects the task image from SWE-bench metadata and sets the workspace root to /testbed. You normally do not need to pass image or memory.

Full Benchmark With Concurrency

Use lower concurrency when your model endpoint, Modal account limits, or benchmark image startup time becomes the bottleneck.

Provider Params

Common Modal overrides live under environments.modal or --env-params:

Image Overrides

Use image for a registry image or named_image for a Modal named image only when intentionally overriding recipe behavior.