Skip to content
clankerwatch

clankerwatch

clankerwatch puts your Claude Code subscription usage in the KDE Plasma panel: the current 5-hour session, the weekly limits, when each one resets, and extra usage. These are the same bars Claude Code’s /usage shows, kept up to date without opening a terminal.

It has two parts:

  • clankerwatch, a small static Go daemon on the D-Bus session bus. D-Bus starts it on demand through a systemd user unit, so there is nothing to enable.
  • The Clanker Watch widget, a Plasma 6 widget written in QML. It binds to the daemon’s D-Bus properties, so updates are pushed to it. It never starts processes and never polls.

How it gets the data

In the default hybrid mode the daemon reads Claude Code’s login from ~/.claude/.credentials.json without ever writing it, and asks api.anthropic.com for your usage at most every 5 minutes while Claude Code is in use and every 20 minutes while it is idle. Whenever Claude Code has fetched usage itself more recently, the daemon uses that cached result instead and saves a request.

In cache-only mode it never reads the login and never uses the network. It shows only what Claude Code has cached, so the bars can be stale.

The daemon never refreshes the login. Refresh tokens are single use, so a refresh by any other program would sign Claude Code out. When the token is about to expire, the daemon waits for Claude Code to refresh it the next time you use Claude Code. Security covers everything it reads and sends.

What you need

RequirementDetail
KDE Plasma6.4 or later
systemdA user session. D-Bus starts the daemon as a systemd user unit
Claude CodeSigned in with a Claude subscription, such as Pro or Max
Architectureamd64 or arm64 Linux

Quick start

Download the package for your distribution from the latest release and install it, then right-click the panel, choose Add Widgets, and add Clanker Watch. Installation has the commands for each distribution and for building from source.

Documentation

  • Getting started: the first run, how the daemon starts, and what the panel and popup show.
  • Installation: packages, building from source, adding the widget, and removing everything.
  • Configuration: the settings page, config.yaml, environment variables, and flags.
  • How it works: data sources, scheduling and backoff, and the D-Bus contract.
  • Security: how the daemon handles Claude Code’s login and what it sends where.
  • Troubleshooting: what each status means and how to fix it.
  • CLI reference: every command and flag.

License

AGPL-3.0-or-later. clankerwatch is an independent project and is not affiliated with Anthropic.