Skip to main content
All configuration options for OpenSRE can be set via environment variables. This page provides a complete reference.

LLM Providers

Anthropic

OpenAI

OpenRouter

DeepSeek

Google Gemini

NVIDIA

MiniMax

Groq

Azure OpenAI

Amazon Bedrock

Ollama (Local)

LLM Reasoning Effort

CLI Investigation Tools

Output & Debugging

Credentials & Authentication

Sensitive variables (*_TOKEN, *_KEY, *_PASSWORD, *_SECRET, and similar) resolve through resolve_env_credential: process env first, then the OS keyring, then the local fallback store described below. Wizard setup dual-writes many of these so a cleared .env still works locally. Exceptions (never stored): webhook and other *_URL values such as SLACK_WEBHOOK_URL and ROCKETCHAT_WEBHOOK_URL stay store / plain env only. They may still embed secret tokens — do not log them unmasked. Set OPENSRE_DISABLE_KEYRING=1 to skip local credential storage entirely; you then have to export every credential in your shell.

When there is no system keychain

Headless Linux, EC2 over SSH, Docker, and CI have no keyring backend, and a macOS login Keychain can be locked. Rather than failing setup, OpenSRE writes the credential to ~/.opensre/credentials.json with owner-only (0600) permissions and tells you it did. Unlock or install a keychain and re-run the command to move the credential back into secure storage. To keep credentials off disk entirely, set OPENSRE_DISABLE_KEYRING=1 and export them in your shell instead. Contributor contract: Credential resolution in Adding tools and integrations (internal contributor markdown in the repo; not a Mintlify docs-site page).

Telemetry & Monitoring

Paths & Directories

Feature Flags

Integration Credentials

Observability & Monitoring

Cloud Platforms

Messaging

Code & Collaboration

Databases

Message Queues & Other Services

MCP Servers

Git Integrations

Multi-Instance Integrations

Many integrations support multi-instance configuration via JSON: See multi-instance-integrations for detailed format.

LLM Classification Models

When not specified, classification models fall back to reasoning models or provider defaults:

Notes

  • All variables support .env file configuration
  • Environment variables take precedence over .env file
  • Variables with empty values are typically treated as “not set”
  • Boolean values accept: 1, true, yes, on (case-insensitive)
  • See LLM Providers for detailed provider setup instructions