Skip to main content

Overview

IronClaw configuration follows this priority: env var > database settings > defaults. Most settings can be configured via the onboarding wizard or by editing:
  • ~/.ironclaw/.env (bootstrap variables)
  • Environment variables in your shell

Database Configuration

Example (PostgreSQL):
Example (libSQL):

LLM Provider Configuration

General

NEAR AI

Example:

Anthropic

Example:

OpenAI

Example:

Ollama

Example:

OpenAI-Compatible

Example (OpenRouter):
Example (LM Studio):

Embeddings Configuration

Example:

Channel Configuration

HTTP Webhook

Example:

Slack Bot

Example:

Telegram Bot

Example:

Signal Channel

Example:

Agent Settings

Example:

Self-Repair Settings

Example:

Heartbeat Settings

Example:

Memory Hygiene Settings

Example:
Identity files (IDENTITY.md, SOUL.md) are never deleted.

Safety Settings

Example:

Secrets Configuration

Example:
Store the master key securely. If lost, encrypted secrets cannot be recovered.

Logging

Example:

Onboarding

Example (remote server):

Complete Example

Here’s a complete ~/.ironclaw/.env file for a typical setup:

Loading Priority

IronClaw loads configuration in this order:
  1. Current directory .env (highest priority, via dotenvy)
  2. ~/.ironclaw/.env (bootstrap variables)
  3. Database settings (from settings table)
  4. Hardcoded defaults (lowest priority)
Environment variables always override database settings.