skip to content
ccdocs

Settings Guide

All CC settings are stored in the SQLite database at ~/.cc-cli/cc_cli.db. The schema lives in cc.config.schema.

How to change a setting

Three entry points, all writing through the same daemon RPC:

  • Single change: cc config — picks the setting from a list, prompts for the new value.
  • First-time walkthrough: cc setup — walks the full sequence (settings + versions + pyenv + shell + theme).
  • Web dashboard: the /settings page in cc web — exposes a subset (GitHub PAT, SH session, IDE, timesheet, auto-fetch, downloads path).

IDE

Drives both cc open (the launcher) and cc switch (the IDE writer plugins that update editor config on each switch).

ValueBehavior
auto (default)Auto-detect — run every writer whose filesystem check matches
codeVisual Studio Code (legacy alias; maps to the vscode writer)
cursorCursor
noneNo editor integration — terminal-only setup
Comma-separated writer namesExplicit selection: vscode,my-plugin

Out of the box cc ships with vscode and cursor writers. Other editors can be added as plugins — see IDE Writers.

Downloads path

The directory CC scans when looking for dump files to restore with cc initdb.

Default: ~/Downloads

Repo structure

How your Odoo source code is organised on disk. CC uses this to know how to fetch updates and which branch to checkout when switching versions.

ValueStructure
multi_dirOne folder per version (odoo-v17/, odoo-v18/, etc.) (default)
single_repoOne shared folder with branch checkouts (odoo/ on branch 17.0, 18.0, etc.)

In single-repo mode, each version must also have a branch configured. Set this via cc workspace add (or cc workspace edit for existing) — the workspace stores the version's branch.

When you switch projects, CC automatically checks out the correct branch in odoo/, enterprise/, and design-themes/.

Multi-version mode

When true, CC maintains one active environment per Odoo version instead of one globally. See Multi-Version Mode for details.

Default: false

Auto-fetch

When true, CC spawns a background git fetch origin across all Odoo repos after each switch, if the fetch interval has elapsed. This keeps the local object store current so that branch checkouts at switch time are near-instant.

Default: false

Auto-fetch interval

How many hours between background fetches.

Default: 24

Timesheet flag threshold

Number of minutes a session must exceed before it is flagged with ⚑.

Default: 60 (1 hour)

Set to a higher value if you prefer less frequent prompts, or lower if you want tighter timesheet discipline.

Prompt on flagged switch

When true, CC shows a confirmation prompt when switching away from a flagged (long) session.

When false, the summary is printed but CC doesn't wait for confirmation.

EOD auto-stop time

HH:MM time-of-day at which CC auto-punches-out if you forget. Blank disables.

Example: 18:30 will close out any open timesheet entry at 6:30 PM the next time you switch.

Color theme

The cc color palette. One of default, purple, chronocoder, custom.

Use cc theme for the dedicated picker (with live preview), or change it via cc config like any other setting.

On this page