Configuration & Project Rules
Set your project rules, CLI settings, environment variables, and ignored files.
This page helps you change how December works in your project and on your computer. December works without any configuration.
1. Project rules (AGENTS.md)
Put an AGENTS.md file in the root of your repository. December reads this file when a session starts and follows the rules in it.
Example AGENTS.md:
# AGENTS.md
## Code standards
- Use TypeScript strict mode.
- Write unit tests with `bun test`.
- Never leave empty catch blocks.
## Commits
- Write all commit messages in lowercase.
- Use the format `feat(scope): description`.
December also reads CLAUDE.md and other rule files. For the full list, see Workspace Memory & Rules.
2. Global settings (~/.december/config.json)
December keeps your settings in ~/.december/config.json. December makes this file when you first sign in or change a setting. The file also holds your saved API keys, so do not share it.
Usually you do not edit this file. Use these commands instead:
/loginto connect a model./modelto select a model./effortto set the reasoning depth./settingsto change the options in the table below.
{
"activeProvider": "anthropic",
"toolPermission": "always-ask",
"thinkingLevel": "deep",
"pathGuard": true
}
Settings
| Key | Values | Default | Description |
|---|---|---|---|
activeProvider | provider name | first one you add | The provider December uses |
activeModel | model ID | provider default | The model December uses |
toolPermission | "always-proceed", "always-ask" | "always-proceed" | If "always-ask", December asks before it edits files or runs commands |
pathGuard | true, false | true | If true, December blocks access to system and credential paths |
nonWorkspaceAccess | true, false | false | If false, December blocks file tools outside your project folder |
thinkingLevel | "fast", "deep" | "fast" | The reasoning depth of the model |
steeringMode | "all", "one-at-a-time" | "all" | How December adds messages that you send while it works |
followUpMode | "all", "one-at-a-time" | "all" | How December adds queued follow-up messages |
browserVisible | true, false | false | If true, December shows the browser window when it uses the browser tool |
mcpServers | object | none | Global MCP servers. See MCP |
Settings for one project
To change settings for one project only, make .december/settings.json in the project root. December merges this file over your global settings:
{
"toolPermission": "always-ask"
}
3. Environment variables
December reads these environment variables:
| Variable | Description |
|---|---|
DECEMBER_CONFIG_DIR | Use a different folder for config.json instead of ~/.december |
DECEMBER_LOGS_DIR | Use a different folder for request logs |
DECEMBER_DISABLE_LOGGING | Set to true to turn off request logs |
CLAUDE_CODE_OAUTH_TOKEN | Use your Claude plan, if you did not connect a model with /login |
To use your own keys, run /login or december key. December saves the key in config.json:
december key anthropic sk-ant-...
4. Ignored files (.decemberignore)
December does not show ignored files when it lists or searches your project. December always ignores your .gitignore patterns and folders such as node_modules, .git, dist, and build.
To ignore more files, make a .decemberignore file in your project root. It uses the same format as .gitignore:
# Generated files
coverage/
# Secret files
.env
.env.local
*.pem
# Large assets
*.mp4
*.zip