LLM Configuration
API key for your LLM provider. Not required for local models or cloud provider auth (Vertex AI, AWS Bedrock).
Price per 1M input tokens in USD for
STRIX_LLM. Use it for gateway or self-hosted model ids that LiteLLM can’t price.Price per 1M cached input tokens in USD for
STRIX_LLM. If unset, cached tokens use the input price.Setting any of these prices replaces the provider-reported and LiteLLM cost for
STRIX_LLM in reports and --max-budget. An unset input or output price counts as 0, so set both. A separate STRIX_DEDUPE_MODEL keeps its LiteLLM price.Select the OpenAI API path for the model:
responses or chat_completions.
By default the model decides: Responses when LiteLLM’s model catalog lists
/v1/responses for it (e.g. gpt-5), chat completions otherwise. A custom
LLM_API_BASE does not change this, so set STRIX_API_TYPE=chat_completions
when your gateway only serves chat completions. Applies to bare and openai/
model names. Also accepts STRIX_FORCE_API.Extra HTTP headers sent on every LLM request, as a JSON object (e.g.
{"X-Feature-Key":"value","X-Tenant":"acme"}). Useful for OpenAI-compatible
gateways that require attribution or routing headers in addition to the bearer
token. The bearer token itself still comes from LLM_API_KEY. Applies to both
the LiteLLM and native OpenAI routing paths.Extra fields merged into the JSON body of every request to the main model, as a JSON object
(e.g.
{"service_tier":"flex","safety_identifier":"9f86d081..."}). Use it
for provider parameters Strix doesn’t expose, such as OpenAI’s service_tier
or safety_identifier. Applies to both the LiteLLM and native OpenAI routing
paths. Fields are not validated, so the provider or gateway must accept them;
unknown fields are usually rejected. Extra fields can override fields Strix
sends and break requests, so don’t set request-shaping fields such as model, messages, input,
tools or stream, and use STRIX_REASONING_EFFORT rather than
reasoning_effort.Seconds the startup connection check waits for the model to answer before
failing with
LLM CONNECTION FAILED. Scan requests use LLM_TIMEOUT.Control thinking effort for reasoning models. Valid values:
none, minimal, low, medium, high, xhigh, max. Defaults to medium for quick scan mode.Send a per-agent
session_id on OpenRouter requests, so each agent’s calls stay on one upstream provider and its prompt cache carries over between turns. When unset, OpenRouter routes every request freely.Token block size that providers cache prompts in. A turn counts as a cache miss in the run report only when the cached tokens fall at least this many tokens short of the previous prompt and the prompt did not shrink. Lower it for providers with smaller blocks (DeepSeek and GLM use 64; vLLM defaults to 16).
Dedicated deduplication model
Finding deduplication is a cheap, structured classification task. By default it runs on the main model, but you can route it to a smaller/cheaper model without affecting the agents that do the actual testing.Model used to judge whether a candidate finding duplicates an existing report.
Falls back to
STRIX_LLM when unset.Optional custom API base URL for the deduplication model. Use when the dedupe
model runs on a different endpoint than the main model.
Optional JSON object of extra HTTP headers sent on every deduplication-model
request, e.g.
{"X-Feature-Key":"value"}. A dedicated dedupe model never
inherits LLM_EXTRA_HEADERS; set this when its endpoint needs custom headers.Optional JSON object of extra request-body fields sent on every
deduplication-model request. A dedicated dedupe model never inherits
LLM_EXTRA_BODY; set this when its endpoint needs them too.Reasoning effort for the deduplication model. Defaults to the model’s own
baseline when unset.
Optional Features
API key for Perplexity AI. Enables real-time web search during scans for OSINT and vulnerability research.
API key for Exa. Enables real-time web search through the Exa
/search endpoint. Exa also powers the web_get_contents tool, which fetches the full text of a page through the Exa /contents endpoint. This is the preferred web search provider.Web search provider:
auto, perplexity, or exa. With auto, Strix uses Exa when EXA_API_KEY is set, and Perplexity otherwise. Set an explicit provider to pin one when you configure both keys.Exa search mode:
auto, fast, instant, deep-lite, deep, or deep-reasoning. Lower modes return results faster. Higher modes plan across more steps and take more time. This setting applies only to the Exa provider.Number of Exa results to return, from
1 to 100. Each result includes a title, a URL, and a short security-focused summary. To read a full page, the agent calls web_get_contents with the result URL. This setting applies only to the Exa provider.Postman API key (
PMAK-…). Enables fetching Postman collections by id as a target (postman://<collection-uid>), and Postman environments (postman://<collection-uid>?env=<environment-uid>) to resolve collection variables. Not needed when passing a local collection export file.Telemetry toggle. Set to
0, false, no, or off to disable telemetry (PostHog, Scarf, OTEL).Record every LLM request’s and tool call’s timing in
run.json, under llm_requests and tool_calls. Adds about 0.5 MB to a typical scan’s run.json.OTLP/Traceloop base URL for remote OpenTelemetry export. If unset, Strix keeps traces local only.
API key used for remote trace export. Remote export is enabled only when both
TRACELOOP_BASE_URL and TRACELOOP_API_KEY are set.Optional custom OTEL headers (JSON object or
key=value,key2=value2). Useful for Langfuse or custom/self-hosted OTLP gateways.Docker Configuration
Docker daemon address, for example
unix:///var/run/docker.sock or tcp://10.0.0.5:2375. When not set, Strix connects to the same daemon as the docker CLI: the current docker context (docker context use), then the default socket. Docker Desktop, OrbStack and Colima register their sockets as contexts, so no extra configuration is needed for them.Sandbox Configuration
Config File
Strix stores configuration in~/.strix/cli-config.json. You can also specify a custom config file: