Reference
Environment Variables
The authoritative list lives in the OSS .env.example. Highlights below.
The full, current set of environment variables — with comments — lives in .env.example on the OSS repo. Read it directly; it's the source of truth and stays in sync with the code.
The headline groups (per .env.example):
- Mode —
IS_STANDALONE,ENVIRONMENT - Database —
POSTGRES_HOST,POSTGRES_USER,POSTGRES_PASSWORD,POSTGRES_DB,POSTGRES_REQUIRE_SSL - Auth —
ADMIN_API_KEY,MEMCLAW_API_KEY - Embedding provider —
EMBEDDING_PROVIDER,OPENAI_API_KEY,OPENAI_EMBEDDING_MODEL(see comments in.env.exampleforlocal/fakeproviders) - LLM enrichment / entity extraction —
ENTITY_EXTRACTION_PROVIDERplus the matching provider key (ANTHROPIC_API_KEY,GEMINI_API_KEY,OPENROUTER_API_KEY, …) - Platform-tier providers — only relevant for the enterprise managed deployment (Vertex AI, platform embedding model). OSS users leave these empty.
Auth modes
Per .env.example:
IS_STANDALONE=true— single-tenant mode. No auth on most routes.ADMIN_API_KEY=…— gates/api/admin/*routes. Required in production.MEMCLAW_API_KEY=…— when set, all non-admin requests must include it viaX-API-Key. Useful when exposing the API beyond localhost.