Skip to content

Demo

Serve canned usage on the D-Bus session bus, cycling through every state the widget shows: normal, warning, critical, extra usage, rate limited, paused, and signed out, about every 12 seconds.

The real engine runs on scripted data, so alerts fire as they would for real. Nothing reads Claude Code’s files or uses the network. Stop the service first, because only one process can own the bus name.

Usage

clankerwatch demo

Examples

Replay states without sending desktop notifications.

systemctl --user stop clankerwatch
clankerwatch demo --notify "" --notify-auth=false

Global options

These settings flags are accepted by every command. See Configuration for how they combine with environment variables and the settings file.

FlagShortDefaultTypeDescription
--claude-config-dir""stringClaude Code’s config directory ($CLAUDE_CONFIG_DIR)
--config""stringYAML settings file, default $XDG_CONFIG_HOME/clankerwatch/config.yaml ($CLANKERWATCH_CONFIG)
--idle-interval20m0sdurationpolling interval while Claude Code is idle ($CLANKERWATCH_IDLE_INTERVAL)
--interval5m0sdurationpolling interval while Claude Code is active, at least 2m ($CLANKERWATCH_INTERVAL)
--log-levelinfostringdebug, info, warn, or error ($CLANKERWATCH_LOG_LEVEL)
--modehybridstringdata source: hybrid, or cache-only to never read credentials or use the network ($CLANKERWATCH_MODE)
--notify80,95stringalert thresholds in percent, empty to turn alerts off ($CLANKERWATCH_NOTIFY)
--notify-authtrueboolalert when the Claude Code login needs attention ($CLANKERWATCH_NOTIFY_AUTH)
--state-dir""stringdirectory for the daemon’s state, default $XDG_STATE_HOME/clankerwatch ($CLANKERWATCH_STATE_DIR)