Configuration File Locations
DevDaily searches for configuration files in the following order:| Scope | Path | Purpose |
|---|---|---|
| Local (per-project) | .devdaily.json | Project-specific settings |
| Global | ~/.config/devdaily/config.json | User-wide defaults |
| Secrets | ~/.config/devdaily/secrets.json or .devdaily.secrets.json | API tokens and webhook URLs |
Local configuration overrides global configuration. Settings are merged, with local values taking precedence.
JSON Schema Support
Enable autocomplete and validation in your IDE by adding the$schema field:
.devdaily.json
- IntelliSense/autocomplete in VS Code, JetBrains IDEs, and other editors
- Inline documentation for all configuration options
- Validation warnings for invalid values
Example Configuration
Here’s a complete example.devdaily.json file:
.devdaily.json
Configuration Categories
Display Settings
Color theme for terminal output
Show ASCII art banners
Enable loading spinners and animations
Use compact output with less whitespace
Command Aliases
Custom command aliases for faster access
Output Preferences
Output formatting and behavior
Git Settings
Git repository configuration
Multi-Project Support
List of projects for cross-project summaries
Currently active project name
Keyboard Shortcuts
Keyboard shortcuts for interactive commands
Journal / Auto-Snapshots
AI/Copilot Settings
GitHub Copilot CLI configuration
Managing Configuration
View Current Configuration
Edit Configuration
Reset to Defaults
Delete the configuration file and rundevdaily init:
Secrets Management
Sensitive values like API tokens and webhook URLs should be stored in a separate secrets file:Environment Variables
Configuration values can also be set via environment variables:Next Steps
Git Hooks
Set up automatic snapshots with git hooks
Project Management
Integrate with GitHub, Jira, or Linear
Notifications
Configure Slack and Discord webhooks
PR Templates
Customize PR descriptions with templates