Docs · setup · Claude

Set up Claude

UsagePool reads the locally authenticated claude executable. The tool needs to be installed and already authenticated on this Mac.

Prerequisites

  • macOS 13 Ventura or newer, on Apple silicon or Intel.
  • Claude Code installed and signed in. Run claude once in a terminal and confirm it answers before enabling the provider.

What UsagePool does with Claude →

02 / 03 · Steps

Four steps to a live meter.

Step 1
Open UsagePool and enable Claude on the first-launch provider screen. Fast local checks identify what is available before any authenticated tool, credential, subprocess or network request is used.
Step 2
General settings opens for setup. Select Claude under Providers and check its connection.
Step 3
Choose a menu bar widget from the available limits. Hover it to see Claude’s current provider card and all reported limits.
Step 4
Optional: consent to status-line capture if you want session and weekly meters that update within seconds while Claude Code is in use.

Fast local checks identify which services are available before any authenticated tool, credential, subprocess or network request is used, so an unconfigured provider costs nothing.

03 / 03 · When it fails

Honest failure modes.

These are the ones you will actually hit, and what each one means.

Claude says Not Installed.
Install Claude Code, open or authenticate it, then refresh the connection in General settings.
Claude says Sign-In Required.
Choose Sign In on the Claude card. UsagePool opens Claude’s supported local login flow in Terminal; return to UsagePool and choose Refresh once authentication finishes.
A weekly model-specific limit has not appeared yet.
It arrives on the terminal workflow’s slower cadence. A limit that is not reported cannot be placed until it appears in a later provider response.
A meter is dimmed or stale.
The last valid reading is still inside its own window but the latest refresh did not produce a trustworthy replacement. Hover its widget for the bounded diagnostic.

Still stuck: known issues lists the constraints that are not bugs, and [email protected] reaches a person.