Skip to main content

Config resolution

Persisted app options in ~/.arden/settings.json take precedence over matching environment values. Provider and service secrets resolve from the process environment, then ./.env, then ~/.arden/.env, with secrets saved through Desktop used only as a fallback. Defaults and provider auto-detection apply after those sources.

LLM providers

Set at least one provider API key, or connect OpenAI Codex with browser sign-in from the desktop client.
Claude Pro/Max OAuth is not supported. Arden will not integrate it until Anthropic officially allows third-party applications to use subscription-based OAuth.
Override auto-detection with explicit model IDs:
Configure role-specific models and reasoning effort in Desktop Settings. They are persisted in model_roles and model_reasoning_efforts in the settings file; the legacy ARDEN_<ROLE>_MODEL variables are not configuration inputs. Choose an embedding model, or No embeddings, in Desktop Settings → Models. Changing it rebuilds the semantic index after confirmation. A disabled choice is persisted as "embedding_model": null.
Embedding is optional. Without it, Arden makes no embedding requests and continues to work with full-text search.

Server

Features

Optional integrations

For Google and Slack, use Settings → Integrations. Use Settings → MCP for MCP servers.

Agent behavior

Deferred tools reduce prompt size and improve cache stability. Gmail, calendar, Slack, automation, background-task, notification, directive, file-write, and MCP tools are loaded on demand. Always-visible tools include local file reads, web search/fetch, research, skills, current time, and load_tools itself.

Authentication

On first arden-server serve, an API key is generated and printed. The server stores only a salted SHA-256 hash – the plaintext key is never persisted.
Desktop clients store the key locally and encrypt it with OS-backed storage when supported.

Settings file

~/.arden/settings.json stores persisted app configuration. Persisted app options override matching environment values; saved provider and service keys remain fallbacks for environment-provided secrets.

Custom models

See Custom Models for registering OpenRouter, Ollama, vLLM, or any OpenAI-compatible endpoint.