;
};
Use the command builder to apply a configuration validated on one task to a complete benchmark evaluation.
After validating one task, use this page to select the model API protocol, benchmark, harness, environment, operating system, and concurrency, then generate a ready-to-run command. The preview updates as selections change, and non-secret options are stored in the page URL so you can return to or share the configuration.
## Before You Scale Up
Before running the complete benchmark, confirm that:
* One representative task has completed successfully with the same model, benchmark, harness, and environment as the complete evaluation. Follow the [Quick Start](/en/get_started/quick_start) for the basic workflow.
* The model endpoint and selected environment have enough capacity, resources, and quota for the target concurrency.
* The required datasets, task images, harness CLIs, and optional dependencies are ready.
* The output directory has enough space for every task's trajectory, logs, and evaluation artifacts.
## Command Builder
Use the command builder below to select the model API protocol, benchmark, harness, environment, concurrency, and other settings. Review the updated preview after changing an option, then run the final command from a shell where the AgentCompass Python environment is active.
Click **Parameters** to enter the model endpoint, model name, and required credentials. If the selected configuration needs other services, the form also shows fields for a judge model, embedding model, search tools, or credentials for the selected Environment. The generated command starts with `agentcompass run` and writes every value directly into the relevant CLI option, including `--benchmark-params`, `--harness-params`, and `--env-params`.
You can save these values in the current browser for reuse on later visits. Clear them when credentials change or are no longer needed.
Saved values are written to the current browser's `localStorage` and reused on later visits. The documentation server does not receive or store them. Do not save credentials on a shared device.
## Frequently Asked Questions
### How should I choose a concurrency value?
Task concurrency sets the maximum number of samples AgentCompass evaluates at once. Increasing it may reduce total runtime, but it also raises model traffic, environment resource usage, and host memory pressure, making throttling or quota exhaustion more likely.
The practical limit depends on model endpoint capacity, the selected environment's resources and quota, and host CPU and memory. Complete a small batch at low concurrency, then increase it gradually while monitoring task startup time, model latency, error rates, and quota usage. If throttling, error rates, or resource pressure increases, return to the last stable value.
### How do I configure options not shown in the builder?
The command builder provides the common settings needed to run a complete evaluation. See [`agentcompass run`](/en/user_guide/using_agentcompass/cli/run#parameter-reference) for other CLI flags and defaults, and [`agentcompass config`](/en/user_guide/using_agentcompass/cli/config#override-order) for configuration precedence. Component-specific fields are documented under [Models](/en/user_guide/modules/models/overview), [Benchmarks](/en/user_guide/modules/benchmarks/overview), [Harnesses](/en/user_guide/modules/harnesses/overview), and [Environments](/en/user_guide/modules/environments/overview). Start with the generated command and add only the overrides required for this evaluation.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.