Read live usage safely

OreoDeck asks macOS Keychain for the existing OAuth credential owned by the selected Claude Code profile, then reads the available usage and account identity for that same profile. The credential needs the `user:profile` scope. OreoDeck does not show, export, or ask you to paste an OAuth token.

Usage is profile-scoped. A successful refresh means the app can read the selected account; it does not grant access to another profile.

Understand the quota rows

A connected account can return a five-hour window, Weekly, Fable weekly, Usage credits, or other limits. Each row includes its used percentage and reset time when Claude returns one. Different plans and accounts can receive different buckets, so an absent row is not an error by itself.

Refresh and re-authenticate

Use Refresh usage for an immediate update, or choose a refresh interval in Settings. OreoDeck only prompts Keychain when it needs the selected profile’s credential. The dashboard labels the result as Live, Last snapshot, or Sign in so stale data is never presented as a successful live request.

When the app says Sign in or re-authenticate, choose Login again and complete Claude Code login in Terminal. Then return to OreoDeck and refresh that same profile; no token transfer is needed.

Troubleshoot unavailable usage

MCP-only OAuth state

Some Claude Code versions store only MCP OAuth state and no usable Claude login credential. OreoDeck marks this as a login-state problem and does not make a background usage request.

Missing user:profile

A token limited to inference cannot read account usage. Sign in again through Claude Code so its credential includes the required `user:profile` scope.

Keychain cannot be read

Unlock the current macOS user session and accept the Keychain prompt for OreoDeck. If access remains unavailable, use Login again rather than copying a credential between profiles.