Configuration
All configuration lives in nexus.config.yaml at your project root. Nexus OS uses a single config file to define project settings, agent behavior, cost controls, trust requirements, and more.
Full Example
yaml
name: my-project
execution:
type: wasm
memoryLimit: 256MB
supervisor:
strategy: one-for-one
maxRestarts: 3
cost:
budget: "$100/day"
alertAt: 80
action: pause
trust:
provider: axis
requirements:
minTrustTier: T3
minTScore: 70
broker:
enabled: true
routing:
preferSkill: true
llmAsLastResort: true
skills:
- name: summarize
handler: ./skills/summarize.wasm
patterns:
- summarize
- summary
- tldr
edge:
provider: cloudflare
regions:
- us
- eu
- asia
agents:
researcher:
source: ./agents/researcher.wasm
cost:
budget: "$10/day"
analyzer:
source: ./agents/analyzer.wasm
cost:
budget: "$5/day"Configuration Sections
| Section | Purpose |
|---|---|
name | Project name identifier |
execution | Runtime settings (WASM sandbox, memory limits) |
supervisor | Default supervisor strategy and restart policy |
cost | Global cost budget, alert threshold, and enforcement action |
trust | AXIS Trust integration requirements |
broker | Broker routing preferences |
skills | Registered skill handlers for broker routing |
edge | Cloudflare Edge deployment settings |
agents | Per-agent configuration overrides |
Environment Variables
Sensitive values should be set as environment variables rather than stored in the config file:
| Variable | Description |
|---|---|
AXIS_API_KEY | AXIS Trust API key for agent verification |
ANTHROPIC_API_KEY | API key for LLM fallback in broker routing |
CF_ACCOUNT_ID | Cloudflare account ID for edge deployment |
CF_API_TOKEN | Cloudflare API token for edge deployment |
Config Validation
Validate your config file without running anything:
bash
naos config validateConfig Precedence
Settings are resolved in this order (highest priority first):
- CLI flags (
--budget 50) - Environment variables (
NAOS_BUDGET=50) nexus.config.yamlvalues- Built-in defaults