cceye

Monitor Claude Code usage costs from local logs with threshold alerts.

Key Features • Installation • Usage • Configuration • Keybindings

Key Features

Claude Usage Log Parsing

Read Claude Code JSONL session logs from your local data directories, recursively scanning all projects and extracting usage from message.usage.

Data roots are discovered in this order:

• CLAUDE_CONFIG_DIR (comma-separated directories, highest priority)
• claude_data_dir from config
• auto-discovered defaults (~/.config/claude/projects, ~/.claude/projects)

Note: When CLAUDE_CONFIG_DIR is set, it overrides all other roots and must resolve to at least one existing projects/ directory. If none of the configured directories contain projects/, cceye errors instead of falling back to claude_data_dir or auto-discovered defaults.

Cost Tracking Modes

Choose how costs are computed:

• auto: use costUSD from log when present, otherwise calculate from token pricing
• calculate: always calculate from token counts
• display: always use costUSD from log (fallback to 0)

Threshold Alerts

Evaluate spend against daily, weekly, and monthly thresholds with warning and critical levels.

Multi-Channel Notifications

Send alerts to:

• Console output
• macOS Notification Center
• Slack webhook
• SMTP email

Live Dashboard (TUI)

Track current costs, hourly trend, model/project breakdown, and notification history in a keyboard-driven terminal dashboard.

Usage Reports

Generate report snapshots with:

• daily
• weekly
• monthly
• session

Each report supports date filters and JSON output options.

Smart Pricing Cache

Pricing is fetched from LiteLLM and cached at ~/.config/cceye/pricing-cache.json (24h TTL), with fallback prices for known models.

macOS Background Service

Install/uninstall a LaunchAgent for background monitoring with log files under ~/Library/Logs/cceye/.

Installation

Prerequisites

• Node.js 20 or later
• Claude Code logs available locally (e.g. ~/.claude/projects)

Install from npm (recommended)

npm install -g cceye

Run without install

npx cceye status

Build from source (development)

git clone https://github.com/ydah/cceye.git
cd cceye
npm install
npm run build

Development checks

npm run typecheck
npm run lint

Usage

Quick Start

If you installed globally, use cceye. If not, replace it with npx cceye.

1. Generate config interactively:

cceye init

1. Edit thresholds and notification settings in ~/.config/cceye/config.yaml.

2. Run a one-shot status check:

cceye status

1. Start daemon mode (foreground, silent):

cceye

1. Start daemon mode with logs (debug):

cceye -d

1. Start dashboard mode:

cceye dashboard

Commands

cceye [command] [--config /path/to/config.yaml]

Commands:
  --version  Print CLI version
  -v         Print CLI version
  (none)     Start daemon mode (silent)
  debug      Start daemon mode with logs
  --debug    Enable debug logs for daemon mode
  -d         Alias for --debug
  dashboard  Start TUI dashboard mode
  status     Run one poll cycle and print current totals (no notifications)
  daily      Print daily usage report
  weekly     Print weekly usage report
  monthly    Print monthly usage report
  session    Print session usage report
  init       Interactive config generator
  install    Install macOS LaunchAgent
  uninstall  Remove macOS LaunchAgent

Notes

• Any command accepts --config <path>.
• Report commands support:
  • --since YYYYMMDD
  • --until YYYYMMDD
  • --json
  • --breakdown
  • --timezone <IANA TZ>
  • --offline
• If not installed globally, run commands with npx cceye <command>.
• Starting with no arguments (cceye) clears notification cooldown flags once before daemon startup.

Configuration

Config file location

Default path:

~/.config/cceye/config.yaml

See config.example.yaml for a complete template.

Key fields

Validation rules

• warning must be less than critical for all windows.
• If Slack is enabled, webhook_url is required.
• If email is enabled, these are required:
  • smtp_host, smtp_port, smtp_user, smtp_pass, from, to

Environment variables

Keybindings

Dashboard Controls

Data Files

Run as a Background Daemon

Option 1: macOS LaunchAgent (recommended)

This is the most reliable way to keep the daemon running in the background on macOS, including after login.

Install

cceye install --config ~/.config/cceye/config.yaml

Uninstall

cceye uninstall --config ~/.config/cceye/config.yaml

Logs

• ~/Library/Logs/cceye/stdout.log
• ~/Library/Logs/cceye/stderr.log

Option 2: nohup (quick/manual)

Use this when you want a simple background process without installing LaunchAgent.

Start

mkdir -p ~/.local/state/cceye
nohup cceye --config ~/.config/cceye/config.yaml > ~/.local/state/cceye/daemon.log 2>&1 &
echo $! > ~/.local/state/cceye/daemon.pid

Stop

kill "$(cat ~/.local/state/cceye/daemon.pid)"
rm -f ~/.local/state/cceye/daemon.pid

Troubleshooting

config file not found

Create ~/.config/cceye/config.yaml or pass --config explicitly.

no session logs found

Verify the following, depending on your environment:

• If CLAUDE_CONFIG_DIR is set: ensure its paths exist and contain Claude session logs, or unset it.
• Otherwise, ensure either:
  • claude_data_dir points to Claude session logs, or
  • one default path exists and contains logs:
    • ~/.config/claude/projects
    • ~/.claude/projects

Slack or Email config errors

When a channel is enabled, all required fields for that channel must be present and valid.

Dashboard terminal capability errors

When running from source, rebuild before running to ensure dist/ is up to date:

npm run build

Development

npm run dev
npm test
npm run test:coverage
npm run build

Migration Notes

• Existing config files remain valid.
• Path resolution is now more flexible:
  • If CLAUDE_CONFIG_DIR is set, those paths are used exclusively.
  • Otherwise, claude_data_dir is used, with auto-discovered defaults appended when available.
• New report commands are available:
  • cceye daily
  • cceye weekly
  • cceye monthly
  • cceye session

License

MIT License.