SupaKeeper Plain comparisons of AI coding tools

Track Claude usage across accounts for Claude Code users

Steps to track Claude usage across several accounts, with options for tools that help and common mistakes to avoid.

By SupaKeeper ยท

SupaKeeper is published by LunarWerx, which makes some of the tools compared here.

Keep one record of each Claude account's usage, check it at a fixed time each day, and note which work moves when an account nears its limit. A tool can automate parts of this. AgentHydra is one option, and it is free. [1]

OptionPriceLicencePlatforms
AgentHydraFree, with no account or subscription [1]MIT License [1]The tray app needs Windows; macOS and Linux builds exist but have not been verified [1]
Other options you comparenot publishednot publishednot published

What you need before you start

Before you track anything, gather every account you use with Claude Code. Write down each account's name, the machine or project it works on, and the plan it is on, so later figures can be read against it. Never write passwords or login tokens into the record.

Find out where each account shows its usage, and confirm that you can open that page. Choose one place to keep the figures, such as a shared spreadsheet or a plain text file, and make sure everyone who works on the project can reach it.

Finally, decide who checks the figures and how often. A tracking habit with no owner tends to lapse, so name that person now.

Step by step

  1. List every Claude account in use, with the machine or project each one serves.
  2. Note the plan each account is on, and where its usage page is.
  3. Create one record with columns for account, date and time checked, usage shown, and the project it supports.
  4. Fill in the record for every account at the same time each day, and again at the start of any long task.
  5. When an account nears its limit, write down which work moves to another account and when.
  6. Each week, compare the totals per account to see whether one account is doing most of the work.
  7. Update the list when someone joins or leaves the project, or when an account is added or removed.
  8. Keep the record in one place only, so no two copies disagree.

The steps work the same whether you use a tool or not. A tool can fill in parts of the record for you, and the next section describes options to check.

Tools that can do it

AgentHydra is made by the team that publishes this site. This page has no verified facts for other tools, so it describes only AgentHydra. Check each other option's own documentation for account support, platforms and pricing before you choose.

AgentHydra shows Claude Code, Codex and OpenCode sessions on your machine in one searchable list, updated live while they run. [1] It lists each Claude and Codex account with its plan and its 5-hour and weekly quota. [1] It shows cost at API list prices by day, model, project and account. [1] The same cost numbers can be printed as JSON from the command line. [1]

It can move a Claude chat, history included, to another of your accounts. [1] For work split across Claude Code sessions, it can move a worker to another account when one nears its limit. [1] Its features are also exposed as tools that an AI assistant can call, including checks of which account the assistant is on and how much quota is left. [1]

It is free, with no account or subscription. [1] It is open source under the MIT License. [1] To install on Windows, run a one-line PowerShell script, download a build from GitHub Releases, or run from source with Bun. [1] The tray app needs Windows; macOS and Linux builds exist but have not been verified. [1] If you work on a Mac or Linux machine, check that build against your own setup before you depend on it.

Common mistakes to avoid

The most common mistake is tracking only the account used most often. Work tends to spread across accounts over time, so one account's figures hide most of the picture.

Another is relying on a single reading. Usage changes through the day, so a reading goes stale quickly. Checking at a set time each day catches that.

Keeping figures only in memory or in a chat message is a third problem. They disappear and cannot be compared later. Writing passwords or login tokens into the record is more serious, so keep those out of every file and message.

Leaving an account off the list after it is added or removed makes every total wrong from that point on. Finally, do not treat any tool's totals as final until you have checked them against the usage page each account shows.

Frequently asked questions

Is AgentHydra free to use for tracking Claude usage?

Yes, AgentHydra is free, with no account or subscription needed. [1] It lists each Claude and Codex account with its plan and its 5-hour and weekly quota. [1] Check that list at the start of each work session before you pick an account for new work. Keeping the figures current this way makes your record more useful over time.

Does AgentHydra work on macOS or Linux?

The tray app needs Windows; macOS and Linux builds exist but have not been verified. [1] If you use a Mac or Linux machine, check that build against your own setup before you rely on it for tracking. The command line tool that prints cost numbers as JSON is another part to check on your system. [1]

How to track Claude usage across several accounts without a tool?

Start with a list of every account, the machine or project each one serves, and its current usage as its own usage page shows it. Record the figures with the date in a shared spreadsheet, and update them at a fixed time each day. When one account nears its limit, write down which work moves to another account. A weekly review of the totals shows where most of the work goes.

Can AgentHydra move a Claude chat to another account?

Yes, AgentHydra can move a Claude chat, with its history, to another of your accounts. [1] Before you move a chat, save any part you will need outside the chat. Then check that the chat appears in the account you moved it to, so you know the move worked before you continue the work there.

Is AgentHydra open source?

Yes, AgentHydra is open source under the MIT License. [1] Read the licence text itself to see the terms before you rely on the tool for work. To install on Windows, you can run a one-line PowerShell script, download a build from GitHub Releases, or run from source with Bun. [1]

Free, with no account or subscription. [1]

Try AgentHydra

Sources

  1. AgentHydra's own description of itself (the product of this site's publisher)

Related comparisons