Configuration Files
Weaver stores configuration in~/.weaver/config.json. You can also use environment variables to override any JSON setting.
Default Configuration
When you runweaver onboard, a default configuration is created:
Agent Configuration
Configure default settings for all spawned agents:Set Workspace Directory
Define where agents can read and write files:Set
restrict_to_workspace to false if you want agents to access files outside the workspace (use with caution).Configure Model Settings
Set the default LLM model and parameters:Parameters:
provider: The LLM provider to use (gemini, openai, anthropic, etc.)model: Model identifier for the providermax_tokens: Maximum tokens in the responsetemperature: Randomness in responses (0.0-1.0)max_tool_iterations: Maximum tool execution loops before stopping
LLM Providers
Weaver supports multiple LLM providers. Configure the ones you need:Supported Providers
Using Environment Variables
For security, use environment variables for API keys:.env
.env files or system environment variables.
Tools Configuration
Configure tools that agents can use:Web Search Tools
Gateway Configuration
Configure the Weaver gateway server for chat channels:- HTTP health check endpoint at
/health - Chat channel webhooks
- Agent communication bus
Heartbeat Service
Keep long-running sessions alive:enabled: Enable/disable heartbeatinterval: Minutes between heartbeat checks (minimum 5)
Device Monitoring
Monitor USB and hardware devices (Linux only):Complete Example
Here’s a production-ready configuration:Configuration Priority
Weaver loads configuration in this order (later sources override earlier ones):- Default configuration (pkg/config/config.go:218)
~/.weaver/config.json- Environment variables
config.json to version control while keeping secrets in environment variables.