Skip to main content

Overview

ArgentOS is configured through ~/.argentos/argent.json. This file controls agent behavior, model routing, channel integrations, gateway settings, storage backends, and more. The configuration is validated against a Zod schema on load. Invalid fields produce clear error messages with paths to the problematic values.

Configuration File Location

Primary: ~/.argentos/argent.json
The state directory (~/.argentos/) can be overridden with the ARGENT_STATE_DIR environment variable. The config file is a symlink target — on systems migrating from OpenClaw, it may symlink to ~/.openclaw/openclaw.json.

Top-Level Sections

agents Section

The agents section contains agent-level defaults and per-agent overrides:

Key Agent Fields

Heartbeat Configuration

Contemplation Configuration

Execution Worker Configuration

Kernel Configuration

models Section

Provider and model configuration:

auth Section

Authentication profiles for multi-provider failover:

channels Section

Channel integrations (Telegram, Discord, Slack, WhatsApp, etc.):
Each channel has its own configuration schema. See the channel-specific documentation for details.

gateway Section

Gateway server configuration:

session Section

Session management configuration:

cron Section

Cron service configuration:

memory Section

Memory backend configuration:

logging Section

approvals Section

Default exec approval settings:

intent Section

Intent governance hierarchy:

hooks Section

Webhook and event hook configuration:

web Section

WebSocket client configuration (for dashboard connections):

Environment Variable Overrides

Several settings can be overridden via environment variables:

Validation

The configuration is validated on load using Zod schemas. Invalid fields produce errors like:
Use config.schema gateway method to retrieve the full schema for programmatic validation.

Key Files