UsageDeck brings usage from several coding assistants into one compact WinUI 3 window. It lives in the notification area, refreshes quietly in the background, and keeps each provider's data separate and easy to scan.
- One compact view for every enabled provider, plus an optional All summary.
- Used or remaining quota percentages, reset countdowns or exact local times, freshness, and error states.
- Optional official service-status monitoring for enabled providers, with incident warnings on affected tabs.
- Per-provider Windows notification rules for limit thresholds and resets, Codex reset credits, provider incidents, sign-in requirements, repeated refresh failures, and recoveries. Settings also reports Windows delivery status and can send a test notification.
- Temporary notification pauses from the tray or Settings for 30 minutes, 1 hour, 2 hours, 4 hours, or until the following morning, with an immediate resume action. Suppressed alerts are not replayed on resume, and problems first detected during a pause do not produce recovery messages.
- Automatic refresh of every enabled provider every 1, 5, 15, or 30 minutes, including while hidden in the notification area, with manual refresh at any time.
- Failed usage checks receive up to two confirmation checks about a minute apart before returning to the normal schedule. Provider-requested waiting periods take priority, including for manual refreshes.
- After a temporary refresh failure, new limit warnings can still appear when fresh data confirms the same usage cycle. Paused alerts are not replayed.
- System, light, and dark themes with optional Mica.
- Settings stored per Windows user in
%LOCALAPPDATA%\UsageDeckData\settings.json, outside the installer-owned application directory. - UsageDeck-branded application, installer, executable, and update packages.
- Built-in updates through versioned Velopack releases, with release-note previews before installation.
- Optional background start at Windows sign-in, with UsageDeck kept quietly in the notification area.
| Provider | Source |
|---|---|
| Codex | Installed Codex CLI app server |
| Claude Code | Authenticated /usage view of the signed-in Claude Code CLI, or an opt-in direct check of Anthropic's usage service |
| Antigravity | Backend quota through the signed-in agy CLI |
| GitHub Copilot | Authenticated GitHub CLI (gh) |
| Kiro | kiro-cli |
| Amp | amp CLI |
| Z.AI | Account-wide personal Coding Plan quota API |
| TheClawBay | Official quota API through a configured key, or theclawbay usage --json through the signed-in CLI |
UsageDeck requires Windows 11 24H2 or later on x64.
- Open the latest release.
- Download the Windows Setup executable, or choose the portable ZIP if you do not want an installed copy.
- Start UsageDeck. First-run setup checks this PC for supported providers and lets you choose providers, theme, and notifications before the first refresh.
The release includes the .NET runtime and the Microsoft-signed Windows App SDK packages required by UsageDeck, so users do not need to install .NET separately. The lightweight launcher registers those packages for the current Windows user before starting the app. If the Windows interface cannot start, UsageDeck displays the error and saves a privacy-safe report under %LOCALAPPDATA%\UsageDeckData\diagnostics. Current builds are unsigned, so Windows may show an unknown-publisher or SmartScreen warning. Each release also includes SHA256SUMS.txt for verifying the downloaded installer or portable ZIP.
The portable ZIP does not install UsageDeck itself, but its first launch registers the same shared Microsoft runtime packages for the current Windows user.
Provider-owned CLIs must already be installed and signed in. Z.AI does not require a CLI; add its API key under Settings → Providers → Z.AI using Windows Credential Manager, the Z_AI_API_KEY environment variable, or session-only storage.
For TheClawBay, open Settings → Providers → TheClawBay and choose Automatic (recommended), TheClawBay CLI, or API key. Automatic prefers a configured API key and falls back to theclawbay usage --json through the signed-in CLI. API keys can be held in Windows Credential Manager, read from the externally managed THECLAWBAY_API_KEY environment variable, or kept in memory until UsageDeck exits.
Most usage collection happens locally through provider-owned tools. UsageDeck does not log tokens, cookies, raw provider responses, or captured terminal output.
- Codex, Antigravity, Copilot, Kiro, and Amp keep authentication under their own tools.
- Claude reads the authenticated
/usageview through Claude Code itself, so sign-in stays with Claude Code. With Claude Code 2.1.178 or later, UsageDeck runsclaude -p /usage, which Claude Code answers locally without a model request, with tools and MCP servers disabled and no session saved. Older versions open/usagein an isolated terminal session with tools disabled, and UsageDeck answers Claude Code's one-time folder trust prompt for its folder only. Both run in UsageDeck's own emptyClaudeProbefolder. UsageDeck reads the plan name from Claude Code's local sign-in file and never writes to that file. Settings → Providers → Claude → Faster direct usage check is off by default. When you turn it on, UsageDeck sends the access token stored by Claude Code only to Anthropic's fixed usage endpoint and falls back to the/usageview if that fails. The direct check also shows limit resets that Claude Code offers through/limit-reset; Anthropic reports these only to a current Claude Code CLI, so this request identifies itself with the installed Claude Code version. Anthropic does not document that endpoint or officially support its use by other apps, and UsageDeck asks you to confirm the risk before enabling it. - Z.AI sends its key only to the fixed endpoint for the selected region and never writes it to the settings file.
- A UsageDeck-managed TheClawBay key is sent only to
https://theclawbay.com/api/codex-auth/v1/quota. CLI mode leaves sign-in under the CLI's ownership, the public status request is unauthenticated, and raw responses are not logged. - Service-status checks use public official endpoints and do not send provider credentials. Providers without a verified public source are labelled unavailable rather than inferred to be operational.
Install the .NET 10 SDK, then run:
dotnet restore src/UsageDeck.App/UsageDeck.App.csproj -r win-x64
dotnet build src/UsageDeck.App/UsageDeck.App.csproj -c Debug --no-restore
dotnet test UsageDeck.slnx -c Debug -p:SkipReleaseArtifacts=true -p:WindowsAppSdkBootstrapInitialize=false --blame-hang-timeout 2m --nologo
& src/UsageDeck.App/bin/Debug/net10.0-windows10.0.26100.0/win-x64/UsageDeck.App.exeVisual Studio users can open UsageDeck.slnx and select the shared UsageDeck launch profile.
In local Debug builds where real update checks are unavailable, the footer update button previews the icons: click Check for updates to show a simulated update, click Download for about four seconds of progress, then click Install to reset to no update. Hover for one second to see the sample release notes. This preview does not download, install, or restart anything and is excluded from Release builds.