skip to content
ccdocs

cc logs

Tail CC daemon and RPC log files from the CLI.

Usage

cc logs              # last 50 lines of cc.log (all logs)
cc logs rpc          # last 50 lines of rpc.log (RPC calls only)
cc logs -f           # follow mode (tail -f)
cc logs -f rpc       # follow RPC log in real time
cc logs -l warning   # filter by log level
cc logs -n 200       # show last 200 lines

Arguments

ArgumentDescription
sourceWhich log to show: all (default) or rpc

Flags

FlagDescription
-f, --followFollow the log in real time
-n, --linesNumber of lines to show (default: 50)
-l, --levelFilter by level: debug, info, warning, error

Log files

FileContent
~/.cc-cli/logs/cc.logAll daemon output — ORM, SQL, RPC, lifecycle (1MB rotating, 5 backups)
~/.cc-cli/logs/rpc.logRPC calls only — method, sanitized params/result, elapsed time (2MB rotating, 3 backups)

RPC log format

2026-05-03 19:34:25,598  OK  pg.list_databases({}) → list[63]  5.4ms
2026-05-03 19:34:25,861  OK  pg.get_db_stats({}) → list[63]  261.9ms
2026-05-03 19:34:26,211  OK  pg.get_last_logins({db_names: …}) → dict[63 keys]  0.0ms

Data is sanitized — lists show list[N], dicts show dict[N keys] or key names, long strings are truncated. No full database lists or sensitive values in the log.

  • cc daemon — daemon lifecycle management
  • cc daemon status — daemon health (uptime, RPC count, DB size, last error)
  • Web companion → /logs — same log data with level/source filters and live auto-refresh

On this page