clawd-usage-winwidget

A tiny floating window + tray icon for Windows that shows how much of your Claude plan limits you've used — the same numbers as /usage in Claude Code, refreshed every minute. And a pixel Clawd who lives in it and reacts to what your sessions are doing.

English · Русский

• Official numbers only. Percentages come from claude -p "/usage" — the slash command runs headless, talks to Anthropic with your existing login and does not call the model or spend tokens.
• No dependencies. Plain Windows PowerShell 5.1 + WPF, which ship with Windows. No Node, no npm, no installer. You only need Claude Code itself.
• Clawd. The crab from Claude Code's welcome screen, built from the same block glyphs and with the same animations. He sleeps when nothing runs, runs around when a session works, waves when a session is waiting for you, sweats near the limit and lies belly-up when it's used up.

Install

Requirements: Windows 10/11 and Claude Code installed and logged in (claude on PATH).

git clone https://github.com/Enhed/clawd-usage-winwidget.git

or download the ZIP and unpack it anywhere. Then double-click start-widget.vbs (it starts the widget silently, without a console window).

Start with Windows — run once in PowerShell from the widget folder:

$a = New-ScheduledTaskAction -Execute "wscript.exe" -Argument "`"$PWD\start-widget.vbs`""
$t = New-ScheduledTaskTrigger -AtLogOn
Register-ScheduledTask -TaskName "clawd usage widget" -Action $a -Trigger $t -RunLevel Limited

Only one copy runs at a time, so a manual start next to autostart is harmless.

Windows hides new tray icons in the overflow (^). To keep it visible: Settings → Personalization → Taskbar → Other system tray icons → clawd-usage-winwidget.

What it shows

• Big number — current session (the 5-hour window), straight from the server. The bar goes green → yellow (60%) → red (85%).

• resets in 3h 03m — time until the window resets, from the exact reset time in /usage.

• WEEK — weekly limit and time to reset. FABLE · WEEK — the separate weekly Fable limit; hidden if /usage doesn't report it.

• SESSIONS — how many Claude Code sessions are running, how many are working and how many are waiting for you. Hover for the list: ▶ working, ? waiting (permission, question, dialog — what exactly is in brackets), ○ idle, plus the folder. Handy for catching a forgotten agent quietly burning your limit.

  Sessions on another machine (a home server, a VM) can be added with remoteSessions in config.json — a list of URLs or file paths, each returning that machine's live sessions in the shape of ~/.claude/sessions/<pid>.json:

  { "generatedAt": "2026-10-17T03:41:47+00:00", "host": "unraid",
    "sessions": [ { "name": "api", "status": "busy", "waitingFor": "",
                    "kind": "interactive", "sessionId": "4b8ca9ab-..." } ] }
  

  The publisher lists only live sessions; cwd is optional. They count for the line and for Clawd and show the host in the hover list. A source that fails, hangs or has a generatedAt older than two minutes adds nothing.

• Service status — green "All Claude systems operational", or yellow/red with the active incident and affected components. Click opens status.claude.com.

• Tray icon — the same percentage as a colored number; the tooltip adds the week and Fable.

• Bottom line — your plan and account email (red "not logged in" if auth expired) and the time of the last /usage answer, marked "stale" if it's old.

The ▾ in the header expands details (remembered between runs):

• LAST 24 HOURS / LAST 7 DAYS — requests, sessions and the "What's contributing to your limits usage?" breakdown from /usage: share on large context, always-on context, subagent-heavy sessions, top MCP servers, skills and subagents. Claude Code itself calls this approximate and counts only this computer.
• LIMITS · 7 DAYS (off by default, showHistory) — the 5-hour (green) and weekly (blue) percentages over the last week, one line each. Hover for the moment under the cursor: the time, both percentages and the project that spent the most in that hour. On the first run the chart is filled from the transcripts that /usage checks of earlier versions left in ~/.claude/projects; after that every /usage answer is a sample in usage-history.json.
• PROJECTS · 7 DAYS — the projects that spent the most this week, by the folder they ran in. Counted from Claude Code's transcripts on this computer: tokens weighted by the model's price, so the shares are an estimate of what went into the limits, not an official figure.
• Version — your Claude Code version. If a newer one is out the line turns yellow: hover for the official CHANGELOG between your version and the latest, click to run claude update in a separate window; otherwise a click opens Claude Code's changelog. Next to it is the widget's own version: hover for what's new in it, click for its CHANGELOG.md on GitHub. When a new release of the widget is out it turns into a yellow "Clawd X is out" (with a Windows notification once per version): hover for what's new, click to download it, replace the files and restart — config.json and the other local files stay. In a git clone the click opens the changelog instead. If the new version does not come up within five minutes, the old one is put back and started again, and the widget says so (and won't offer that version again).

Left-click the tray icon to show/hide the window; right-click for the menu: show/hide, refresh, settings, exit. Drag the window anywhere — the position is saved.

Settings — the gear in the window's header (or the tray menu): language, theme, Clawd's skin picked from cards with a live preview (he raises his arms under the mouse), size, opacity, always on top, which blocks the window shows, the tips, the chat, recurring tasks and Clawd's session. Everything applies at once; the rest of the keys are in config.json, linked at the bottom.

The Claude Code tab is Claude Code's own ~/.claude/settings.json, a picked set of what is otherwise easy to miss: the model of new sessions, fast mode, language of answers, the permission mode at start, auto-compact, auto memory, checkpoints for /rewind, the byline in commits, how long sessions are kept, the update channel, the terminal theme and renderer, the answer style, the transcript view, tips, pushes to the phone and more — each with a hint on hover. Only the changed key is rewritten, the rest of the file stays as it was; the file as it was before the first change is kept as settings.json.clawd-bak. Changes take effect in new sessions, and Clawd's chat uses them too.

Clawd

The three hearts in the header are his health, tamagotchi-style: how much of the session limit is left. Each half-heart is about 16.7%; zero hearts only at 100%. Health changes how he behaves on top of everything above — full of energy he walks faster and hops, tired he yawns and slows down, barely alive he staggers, sweats and sometimes trips over.

Right-click Clawd for developer mode: force