~/.cynative/config.yaml on startup. Every value in that file can also be set through a CYNATIVE_* environment variable — env vars take precedence over the file. For simple setups (picking a provider, pointing at an API endpoint) you do not need a YAML file at all: export a handful of env vars and you are running.
Config file location
The default config file path is~/.cynative/config.yaml. Pass --config <path> to use a different file:
--config path exists, Cynative starts with built-in defaults and whatever CYNATIVE_* env vars are set. A missing file is not an error; an unreadable or malformed file is.
Maps and slices (for example
llm.keys[], connectors.github.permissions, and llm.network_config.extra_headers) require YAML — they cannot be expressed as a single env var. Every other field is env-bindable.LLM configuration
Thellm: block configures the model provider. provider and model are required; everything else has a default or is optional.
LLM field reference
extra_headers and keys[] require YAML. See LLM Providers for every supported provider’s full configuration reference, including provider-specific key configs (Azure endpoint, Bedrock region, Vertex project, Ollama URL, etc.).
Session limits
These knobs bound how much work a single run can do — essential for unattended, scheduled, or CI runs.
Finding verification (
verify_findings) makes additional model calls — budget for them on any run that produces findings.
Display configuration
Audit configuration
Every tool call is recorded to a persistent JSONL audit log. The log is fail-closed: if a call cannot be recorded, the run aborts. Tool results are redacted before they are written; approval-prompt arguments are stored verbatim, so the log can hold sensitive values. The log is readable only by the user who ran Cynative.
Every entry from an agent run also records the agent’s name, source, and file digest, so a finding can be traced to the exact prompt that produced it.
Cache configuration
Cynative maintains an on-disk cache for connector hardening metadata — IAM policy documents, service catalogs, OpenAPI descriptions, and model archives — so startup is fast on repeated runs.Connector configuration
Theconnectors: block lets you configure each connector’s read-only policy ceiling. Defaults are secure; you only need this block if you are using a custom policy ARN, role, or permission set. Each connector also has its own credential discovery and full reference in the Connectors section.

