Credentials. Refresh sends each saved account's own tokens to Anthropic's usage endpoint, so make sure those accounts are yours to query.
Who it is forA developer with several Claude Code accounts who needs to decide which one to use for a big task today.
The problemUsage limits are shown only as of the last session, so an account that is not signed in can show figures that are stale.
The outcomeEach saved account shows its current five-hour and weekly usage after Refresh, so you can pick the one with the most headroom.
What you need first
- A Mac running macOS (the README says macOS only)
- Claude Code or Codex installed and signed in to at least one account
- Homebrew, or a manual download of the latest .dmg from Releases
- Xcode Command Line Tools if you build from source
Steps
- Install Janus with
brew install --cask --no-quarantine ramitvishwakarma/tap/janus, or download the .dmg from Releases and open it. - Save each Claude Code account using Save current account, switching accounts as described in the Janus README.
- Open the Janus window and press Refresh to fetch current usage for each saved account.
- Read the line under each pair of bars to confirm whether a figure was fetched or came from the last session.
- Switch to the account with the most limit left, then restart Claude Code.
Prompt for your agent
Using the Janus repo at RamitVishwakarma/Janus, describe how to refresh usage figures for all saved Claude Code accounts in Janus. Output a table of each account with its five-hour and weekly usage and whether each figure was fetched or cached. Verify that the figures for the signed-in account match Claude Code's own limits display.
Caveat. The signed-in account's token is never renewed by Janus, so its figures depend on Claude Code keeping the session current.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page