Host Process

Run lightweight benchmark and harness operations directly on the AgentCompass machine.

host_process executes environment commands directly on the machine running AgentCompass. It has the lowest startup overhead, but it does not provide container isolation, resource limits, or outbound network enforcement.

Use it only when the selected benchmark and harness are designed for local execution and do not require a prebaked task image. Prefer Docker, Daytona, or Modal for repository repair, terminal tasks, untrusted commands, or reproducible sandbox state.

A harness running through host_process can read and modify files accessible to the current user and can use the host network. Do not use it for untrusted agent-generated shell commands.

Basic Run

The CLI defaults to host_process when --env is omitted. Specify it explicitly in shared commands so the execution location remains clear:

export MODEL_NAME=""
export MODEL_BASE_URL=""
export MODEL_API_KEY=""

agentcompass run <benchmark> <harness> "$MODEL_NAME" \
  --env host_process \
  --model-base-url "$MODEL_BASE_URL" \
  --model-api-key "$MODEL_API_KEY"

Before running, confirm that the benchmark page lists host execution as supported and that every required local tool or service is installed.

Provider Params

Field	Default	How to use it
workspace	.	Directory against which relative file and command paths are resolved. Point it at a dedicated disposable workspace rather than an important checkout.
default_workspace_root	workspace/	Fallback workspace exposed to a harness when the benchmark does not provide one.

Override the workspace for one run:

export MODEL_NAME=""

agentcompass run <benchmark> <harness> "$MODEL_NAME" \
  --env host_process \
  --env-params '{"workspace":"/path/to/disposable-workspace"}'

Use agentcompass config docs env host_process to inspect the live schema.

Network and Resources

host_process supports only the public network mode and cannot switch policy between setup, agent rollout, and verification. CPU, memory, disk, process, and filesystem access are controlled by the operating system account rather than environment parameters.

If a run needs no-network, an allowlist, per-task resource limits, task images, or disposable state, select an isolated provider:

Need	Recommended provider
Local task image and resource limits	Docker
Managed remote development sandbox	Daytona
Elastic cloud sandbox and placement controls	Modal

Troubleshooting

Symptom	What to check
Command or executable not found	Install it on the host or select a sandbox image that contains it.
Permission denied	Check the current user, workspace ownership, executable permission, and parent-directory access.
Files appear in an unexpected checkout	Set an explicit absolute workspace and inspect the benchmark-prepared workspace in the resolved plan.
Benchmark requires a prebaked repository or task image	Use a compatible Docker, Daytona, or Modal recipe.
Network policy is rejected	host_process cannot enforce restricted policies; choose an isolated provider.

Related Pages

• Choose an Environment
• Network Policy
• Sandbox Resource Limits
• Troubleshooting Runs