Environment Variables¶
Overview¶
Swarms uses environment variables for configuration management and secure credential storage. This approach keeps sensitive information like API keys out of your code and allows for easy configuration changes across different environments.
Core Environment Variables¶
Framework Configuration¶
Variable | Description | Example |
---|---|---|
SWARMS_VERBOSE_GLOBAL |
Controls global logging verbosity | True or False |
WORKSPACE_DIR |
Defines the workspace directory for agent operations | agent_workspace |
LLM Provider API Keys¶
Tool Provider Keys¶
Security Best Practices¶
Environment File Management¶
- Create a
.env
file in your project root - Never commit
.env
files to version control - Add
.env
to your.gitignore
:
API Key Security¶
Important Security Considerations
- Rotate API keys regularly
- Use different API keys for development and production
- Never hardcode API keys in your code
- Limit API key permissions to only what's necessary
- Monitor API key usage for unusual patterns
Template Configuration¶
Create a .env.example
template without actual values:
# Required Configuration
OPENAI_API_KEY=""
ANTHROPIC_API_KEY=""
GROQ_API_KEY=""
WORKSPACE_DIR="agent_workspace"
# Optional Configuration
SWARMS_VERBOSE_GLOBAL="False"
Loading Environment Variables¶
from dotenv import load_dotenv
import os
# Load environment variables
load_dotenv()
# Access variables
workspace_dir = os.getenv("WORKSPACE_DIR")
openai_key = os.getenv("OPENAI_API_KEY")
Environment Setup Guide¶
Environment-Specific Configuration¶
Troubleshooting¶
Common Issues¶
Environment Variables Not Loading
- Verify
.env
file exists in project root - Confirm
load_dotenv()
is called before accessing variables - Check file permissions
API Key Issues
- Verify key format is correct
- Ensure key has not expired
- Check for leading/trailing whitespace
Workspace Directory Problems
- Confirm directory exists
- Verify write permissions
- Check path is absolute when required