FastClaw Docs
Core

Configuration

Bootstrap env vars and database-backed runtime settings.

FastClaw uses two configuration layers:

  1. Bootstrap env vars: process-level settings read from FASTCLAW_* at startup.
  2. Runtime settings: providers, channels, tool policy, agent defaults, sandbox toggles, and plugin config stored in the database and edited through the dashboard or CLI.

There is no fastclaw.json.

Bootstrap Variables

VariableDefaultPurpose
FASTCLAW_HOME~/.fastclawHome directory for DB, skills, workspaces, logs
FASTCLAW_PORT18953Gateway HTTP port
FASTCLAW_BINDloopbackloopback for 127.0.0.1, or all for 0.0.0.0
FASTCLAW_STORAGE_TYPEsqlitesqlite or postgres
FASTCLAW_STORAGE_DSNemptyPostgres DSN, or empty for SQLite at $FASTCLAW_HOME/fastclaw.db
FASTCLAW_STORAGE_AUTO_MIGRATEtrueApply schema migrations on boot
FASTCLAW_REDIS_ENABLEDfalseEnable Redis-backed bus and channel leases
FASTCLAW_REDIS_ADDRemptyRedis address, e.g. redis:6379
FASTCLAW_SANDBOX_ENABLEDdashboardOverride sandbox runtime toggle
FASTCLAW_SANDBOX_BACKENDdocker pathdocker, e2b, or boxlite
FASTCLAW_SANDBOX_IMAGEbackend defaultSandbox image/template
FASTCLAW_LOG_LEVELinfodebug, info, warn, error
FASTCLAW_DEBUG_MODEfalseVerbose diagnostics, including prompt dumps

Object Store Variables

Distributed deployments can hydrate skills/files from S3-compatible storage:

FASTCLAW_OBJECT_STORE_TYPE
FASTCLAW_OBJECT_STORE_REGION
FASTCLAW_OBJECT_STORE_BUCKET
FASTCLAW_OBJECT_STORE_PREFIX
FASTCLAW_OBJECT_STORE_ACCESSKEY
FASTCLAW_OBJECT_STORE_SECRETKEY
FASTCLAW_OBJECT_STORE_ACCOUNTID
FASTCLAW_OBJECT_STORE_ENDPOINT
FASTCLAW_OBJECT_STORE_USESSL

Runtime Settings

Runtime settings are edited from the dashboard and stored in the database. Examples:

  • Providers and model catalog
  • Agent default model and policy
  • Channel credentials
  • Tool categories and tool providers
  • Sandbox toggle, backend, image, and network policy
  • Plugin configuration
  • Scheduler, memory, heartbeat, privacy, object store

CLI commands such as fastclaw agents config <agent> set <key> <value> write through the same store the dashboard uses.