How to run Rogue evaluations from the command line.
Argument | Required | Default Value | Description |
---|---|---|---|
—workdir | No | ./.rogue | Directory to store outputs and defaults. |
—config-file | No | <workdir>/user_config.json | Path to a config file generated by the UI. Values from this file are used unless overridden via CLI. If the file does not exist, only cli will be used. |
—evaluated-agent-url | Yes | The URL of the agent to evaluate. | |
—evaluated-agent-auth-type | No | no_auth | Auth method. Can be one of: no_auth , api_key , bearer_token , basic . |
—evaluated-agent-credentials | Yes* if auth_type is not no_auth | Credentials for the agent (if required). | |
—input-scenarios-file | Yes | <workdir>/scenarios.json | Path to scenarios file. |
—output-report-file | No | <workdir>/report.md | Where to save the markdown report. |
—judge-llm-model | Yes | Model name for LLM evaluation (Litellm format). | |
—judge-llm-api-key | No | API key for LLM (see environment section). | |
—business-context | Yes* Unless --business-context-file is supplied | Business context as a string. | |
—business-context-file | Yes* Unless --business-context is supplied | <workdir>/business_context.md | OR path to file containing the business context. If both given, --business-context has priority |
—deep-test-mode | No | False | Enables extended testing behavior. |
—debug | No | False | Enable verbose logging. |
<workdir>/user_config.json
and use it if it exists.
The config file is a JSON object that can contain all or a subset of the fields from the CLI arguments, except for --config-file
.
Other keys in the config file are ignored.
Just remember to use snake_case keys. (e.g. --evaluated-agent-url
becomes evaluated_agent_url
).
--business-context
or --business-context-file
must be provided../.rogue/business_context.md
./.rogue/user_config.json