.env when you want to override something or add API keys.
Config paths
Override with
ARKA_CONFIG_DIR (or CONFIG_DIR), INSTALL_HOME (legacy ARKA_HOME), or ARKA_CACHE_DIR (or CACHE_DIR).
Setting ARKA_CONFIG_DIR=/path/to/my-arka-config moves all user config there: .env, mcp.json, hub/, agent-memory/, skills/, and related paths.
.env, charts.yaml, llm-skill-models.json, and skills/ (plugins).
Precedence
Placeholder values like
your_gemini_api_key_here are ignored.
Key names
Prefer short names. LegacyARKA_* keys still work (ARKA_ROUTE_MODE → ROUTE_MODE):
Built-in defaults
Web search failures are non-fatal: if DuckDuckGo times out or errors on every retry, chat logs the error and answers from model knowledge instead of stalling. Tune both knobs when you’re on a slow or flaky network:
Essential API keys
Optional extras
Install feature groups as needed:Applying changes
arka setup seeds ~/.config/arka/.env from the package template on first install.
Full reference
Canonical env reference:src/arka/env.example (~500 lines) in the repo.
See LLM orchestration for failover details. See Security for security layers. See Troubleshooting for common fixes.