You typed clawdmeter. You meant ClaudeMeter.

No. The product is ClaudeMeter, written as one word with a capital C and a capital M, and spelled like the model name 'Claude'. The 'clawd' spelling is what people type when they sound the name out and skip the silent letters; it shows up in real Google Search Console impressions for claude-meter.com. The repo on GitHub is m13v/claude-meter; the brew cask is m13v/tap/claude-meter; the website is claude-meter.com. If a result, a tweet, or a README spells it 'clawdmeter', 'clauwdmeter', 'cloudmeter', or 'clauwmeter', it is almost certainly pointing at the same project.

It puts your live Claude Pro or Max plan usage in your macOS menu bar. Three numbers: the rolling 5-hour window percent (with reset time), the weekly quota percent (all models and Opus separately, with reset time), and your Extra Usage dollar balance for the metered billing Anthropic rolled out in April 2026. It reads those numbers from the same three internal endpoints that claude.ai/settings/usage renders, so the percents match exactly with what you see in the Settings page when both are open.

One command: brew install --cask m13v/tap/claude-meter. That puts the menu bar app in /Applications/ClaudeMeter.app and a CLI at /Applications/ClaudeMeter.app/Contents/MacOS/claude-meter. Then load the browser extension once: clone github.com/m13v/claude-meter, open chrome://extensions in Chrome, Arc, Brave, or Edge, turn on Developer mode, click Load unpacked, and pick the extension/ folder. Visit claude.ai once. The menu bar popover lights up within 60 seconds. No cookie paste, no API key, no login screen for the app itself.

Two reasons. The first is phonetics: spoken out loud, 'Claude' sounds like 'clawd', so when someone has only heard the name (a podcast, a Discord call, a colleague mentioning it in a meeting) they often type the phonetic version into Google. The second is muscle memory from the word 'cloud'; people typing fast on autocomplete-aggressive iOS keyboards land on 'cloud' or 'clawd' before they realize the product name is the Anthropic model. Google's autosuggest and Search Console treat 'clawdmeter' as a distinct query from 'claudemeter', which is why the misspelling shows up as its own row in our impressions data.

Yes. All four are the same project. The GitHub repo is m13v/claude-meter, the npm-like brew cask name is claude-meter, the website is claude-meter.com, and the in-product display name with no space and capital letters is ClaudeMeter. The hyphen exists because Cargo, Homebrew, and DNS prefer lowercase-with-hyphens; the camel-case 'ClaudeMeter' exists because that is how the macOS .app bundle is labeled in the Dock. The misspellings ('clawdmeter', 'cloudmeter', 'clauwdmeter') are not separate forks.

Four checks. One: the brew tap is m13v/tap, owned by the same GitHub account that owns the source repo. Two: the cask URL points at a release artifact under github.com/m13v/claude-meter/releases, signed and notarized by the developer account. Three: the menu bar app's About panel links to https://claude-meter.com, not a lookalike domain. Four: the source for the data fetch is one file, src/api.rs, which you can read in 90 seconds; it hits three URLs under claude.ai, no third-party servers. The MIT license at the repo root means you can audit the binary against the source without asking permission.

That is the bridge the menu bar app listens on. When the extension fetches your usage from claude.ai with your already-logged-in cookies, it POSTs the snapshot to http://127.0.0.1:63762/snapshots. The number is fixed in extension/background.js so the manifest can declare it as a host permission, and it is bound to 127.0.0.1 only, so nothing on your network can reach it. The menu bar app reads incoming snapshots, identifies which browser sent each one by looking up the peer TCP socket's owning process, and updates the icon. If you grep the repo for '63762' you find exactly two lines: extension/background.js:2 and extension/manifest.json:9.

No. There is no automatic redirect from typo'd brand domains to claude-meter.com; we do not own and would not buy 'clawdmeter.com'. You probably typed 'clawdmeter' into Google or Bing, the search engine matched it against pages from claude-meter.com that mention the product (or against this page now that it exists), and clicked through. The URL bar still shows whatever you typed. If you want to bookmark the real thing, the canonical address is https://claude-meter.com.

They measure different numbers. ccusage and Claude-Code-Usage-Monitor read the JSONL files Claude Code writes locally under ~/.claude/projects/, parse the prompt/response token counts out of those logs, and aggregate them. That is useful for per-project cost accounting, but the number does not include any usage that happened on claude.ai itself, on Claude Code on another machine, or before the JSONL window. ClaudeMeter polls claude.ai/api/organizations/{org_uuid}/usage instead, which is the server-truth number Anthropic's rate limiter actually compares against. The two are complementary; the percent that 429s you is the ClaudeMeter one.

ClaudeMeter is macOS 12+ only right now. Linux and Windows are not on the roadmap because the cookie-decrypt path depends on macOS Keychain APIs and the menu bar UI depends on SwiftUI. The browser extension by itself runs on any Chromium browser on any OS and will happily fetch and POST snapshots, but with no local bridge to receive them the data has nowhere to land. If you only want the data and not the menu bar UI, the three endpoints in src/api.rs work from any HTTP client; you can build a CLI tracker in 30 lines of Python.