Configuration
Environment Variables
Core local configuration lives in .env.local.
Important values:
ACCESS_KEY=<your-access-key>
CREDENTIAL_SECRET=<auto-generated>
SWARMCLAW_EXTENSION_FAILURE_THRESHOLD=3
SWARMCLAW_EXTENSION_FAILURE_THRESHOLD controls when repeatedly failing external extensions are auto-disabled.
Data Directory
Persistent data lives under data/:
| Path | Contents |
|---|---|
data/swarmclaw.db | app metadata such as agents, chats, tasks, schedules, projects, goals, connectors, webhooks, settings, activity, and usage |
data/memory.db | durable memory, knowledge chunks, embeddings, and knowledge-source grounding data |
data/uploads/ | uploaded and generated files |
data/extensions/ | installed external extension files |
data/extension-failures.json | external extension failure metadata |
Ollama Local vs Cloud
Ollama mode is an explicit stored choice on agents and chats:
- Local uses the configured local/self-hosted endpoint.
- Cloud uses Ollama's hosted path with a credential.
If you route a cloud-named model through local Ollama, the explicit Local selection still wins.
Canonical Capability Model
Persisted agents and sessions store:
toolsextensions
The older plugins field is not the canonical app model anymore.
Settings UI
Current settings areas are organized around:
- General
- Appearance
- Agents & Automation
- Memory & AI
- Integrations
Important sections include:
- user preferences
- capability policy
- storage and uploads
- automation limits
- heartbeat
- supervisor and reflection
- embeddings
- skills
- memory governance
- voice
- web search
- providers
- secrets
Structured Sessions are a core feature, not an extension or separately enabled engine.
Runtime and Loop Controls
Key operator-facing controls live under the automation settings:
- global automation limits
- daemon autostart behavior
- heartbeat defaults
- supervisor and reflection settings
- estop resume approval behavior
Autonomy incidents and estops are surfaced in the dedicated Autonomy page.