CCManager supports per-project configuration files that allow you to customize settings for individual projects. Project configurations are automatically merged with global settings, with project settings taking priority.
- Project config location: Place a
.ccmanager.jsonfile in the git repository root - Merge behavior: Project config is merged with the global config (
~/.config/ccmanager/config.json) - Priority: Project settings always take precedence over global settings
You can configure project settings in three ways:
- Through the UI: Select Project Configuration from the main menu
- Configuration file: Directly edit
.ccmanager.jsonin your project's git repository root - With an AI coding agent: install the
ccmanager-configskill, which teaches Claude Code or Codex the full configuration schema and ships a validator
Example .ccmanager.json:
{
"commandPresets": {
"presets": [
{
"id": "gemini",
"name": "Gemini",
"command": "gemini",
"detectionStrategy": "gemini"
}
],
"defaultPresetId": "gemini"
},
"shortcuts": {
"returnToMenu": {
"ctrl": true,
"key": "e"
}
}
}All options available in the global config can be used in the project config.
Note that CCManager reports nothing when a config file is wrong: a file that is not valid JSON is discarded whole, and unrecognized keys are ignored silently. To check a file before wondering why a setting has no effect:
node plugins/ccmanager-config/skills/ccmanager-config/scripts/validate-ccmanager-config.mjs .ccmanager.json- Multi-project mode: Project configuration is not available when running CCManager with the
--multi-projectflag. In multi-project mode, only global configuration is used.