Host Process

host_process runs tasks directly on the host that is running AgentCompass. It is the default provider and has the lowest startup overhead, but it does not isolate processes, files, resources, or network access. Use it only for trusted workloads that explicitly support local execution.

Linux and WSL 2 are fully supported. On macOS, use this provider only for lightweight workloads that the benchmark documentation explicitly supports. Native Windows is not supported.

Agent commands run with the current user’s permissions. They can read, modify, or delete any file that user can access. Do not use host_process for untrusted commands.

Before You Start

Make sure that:

• the benchmark and harness explicitly support host_process;
• all required commands, Python packages, and local services are already available;
• workspace points to a dedicated disposable directory, not an important repository or data directory.

host_process needs no additional credentials. It inherits the environment of the user that starts AgentCompass.

Validate the Configuration with run

Omitting --env also selects host_process. The example writes the provider explicitly and uses sample_ids to run one task, making the execution location easy to verify first:

agentcompass run <benchmark> <harness> "$MODEL_NAME" \
  --env host_process \
  --benchmark-params '{"sample_ids":["<sample-id>"]}'

Replace the placeholders with your benchmark, harness, and sample ID. The command above is a minimal agentcompass run check; see agentcompass run for model endpoint and other shared options.

host_process also supports agentcompass launch. Put shared settings under defaults.environment in the orchestration file, or request-specific settings under requests[].environment; write id: host_process and the provider parameters at the same level. See the launch mapping rules.

Parameter Reference

Pass parameters with --env-params, or place them under environments.host_process in a configuration file.

For example, create a dedicated workspace, then add the following option to the agentcompass run command above. Replace the value with an existing absolute path:

--env-params '{"workspace":"/path/to/disposable-workspace"}'

Connection and Credentials

host_process has no connection or credential parameters. Tasks directly inherit the identity and host environment of the user that starts AgentCompass.

Image and Startup

host_process creates no image or sandbox, so it has no image or startup parameters. Task commands use the programs and dependencies already installed on the host.

Identity and Metadata

host_process creates no independent remote resource or container, so it has no execution-instance name, tag, or other provider metadata parameters.

Workspace and Environment Variables

Field	Default	Meaning
workspace	.	Existing host directory where commands run and provider-relative paths are resolved. A relative value is resolved from the working directory in which AgentCompass starts; prefer an absolute path to a dedicated workspace.
default_workspace_root	workspace/	Fallback workspace given to the Harness when the Benchmark does not specify a task working directory. It can be absolute; a relative value is resolved under workspace, but it does not change the command working directory set by workspace.

host_process has no separate environment-variable parameter. Task processes inherit the host environment variables present when AgentCompass starts.

Resources

host_process has no CPU, memory, or disk limit parameters. Tasks share resources with other host processes, and the host operating system controls scheduling and limits.

Network

host_process has no provider-specific network parameters and supports only public from the shared network policies. Host network configuration and permissions control outbound access.

Lifecycle and Timeouts

host_process creates no sandbox whose lifecycle must be managed, so it has no provider-specific lifecycle or timeout parameters. Use Run Controls for the overall evaluation timeout.

Parameter Sources

• Run agentcompass config docs env host_process to see the fields, types, and defaults supported by your installed AgentCompass version.
• host_process has no independent upstream provider. AgentCompass, the host operating system, and the current user environment determine command, path, and permission behavior.

Provider-Specific Behavior

• There is no isolation. Tasks share the host filesystem, process permissions, installed tools, and environment variables.
• Only public network access is supported. This provider cannot restrict egress or switch policies between setup, agent execution, and verification. See Network Policy.
• There are no provider-level resource limits. The operating system manages CPU, memory, and disk use. See Resource Limits.
• No sandbox is created or cleaned up. --keep-environment has no practical effect for this provider.

Troubleshooting

Symptom	What to check
A command or Python package cannot be found	Make sure it is installed in the same environment that starts AgentCompass, and check PATH.
A relative path resolves to the wrong location	Set workspace to an existing absolute path.
A file operation is denied	Check the current user, ownership, and parent-directory permissions.
A network policy is rejected	host_process supports only public; use Docker, Daytona, or Modal when isolation is required.
The benchmark requires a task image	Use one of the container or remote providers listed by that benchmark.

Related Pages

• Environments Overview
• Configure an Environment
• Run Controls
• Installation and Platform Support