Configuration
Configuration
Config files, environment variables, runtime settings, and secrets.
Facio can be configured through files, environment variables, Placet settings, the management API, and runtime commands. Docker quickstart uses environment variables for the first boot, then the running agent can persist settings through the same config model.
Main config areas
| Area | What it controls |
|---|---|
agents.defaults | Workspace, model, provider, token limits, concurrency, sessions, goals, Reflection, self-improvement. |
providers | API keys, API bases, extra headers/body per provider. |
channels | Placet, Telegram, Slack, Discord, Email, Teams, transcription, progress visibility. |
api | HTTP API host, port, management token, A2A token, CORS, rate limit. |
gateway | Gateway/server host, port, heartbeat settings. |
tools | Web, exec, browser, MCP servers, guardrails, policy. |
audit | Audit storage, preview size, retention intent. |
logging | Persistent log file behavior. |
How settings are applied
- Docker Compose envs provide initial runtime values.
- Placet settings and
PATCH /api/v1/settingspersist changes to config. - Provider credentials can be changed without returning raw values.
- Some settings hot-apply to the running loop; others return
restart_needed. - Secrets should go through the credential store, not plain docs or prompts.
Pages
| Page | Use it for |
|---|---|
| Environment variables | Quickstart envs and stable Facio env overrides. |
| Credentials | Secret storage, provider keys, placeholders, and exposure boundaries. |