SupaKeeper Plain comparisons of AI coding tools

How to review agent history for billing for AI consultants in 2026

Learn how AI consultants can review agent history to build a billing record for clients.

By SupaKeeper ยท

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

To review agent history for billing, gather the agent sessions that ran for each client, collect the cost or usage figures your tool records for those sessions, and check the numbers against the accounts and projects you bill for.

OptionWhat it can doWhat to check
AgentHydraShows Claude Code, Codex and OpenCode sessions on your machine in one searchable list, updated live while they run. [1] It shows cost at API list prices by day, model, project and account. [1]Check whether its session view and cost figures match the accounts, projects, and time ranges you bill for.
Existing workflowUses the session views and billing records already available in the consultancy.Check whether the current approach collects every session and gives the cost details needed for each client.
Manual recordA record kept for billing that lists sessions and the usage tied to each client.Check which sessions it captures and how cost is reported for each billing period.

What you need before you start

Before agent history can become a client bill, gather the records that tie work to money. These are the agent sessions run for each client, the cost or usage figures those sessions produced, and the accounts and projects the sessions belong to.

Know which agents and sessions belong to which client. A billing review starts by separating work done for one client from work done for another client or for the consultant's own projects.

Collect the numbers that describe the usage. Look for the cost or usage figures the tool records, and note the time range each invoice has to cover.

Understand how the tool counts cost. Some tools report usage in their own terms instead of a billed amount, so confirm what the numbers mean before they reach an invoice.

Keep the account and plan details for each session. The plan a session ran under can change how the usage is priced, and the account shows which client the work should be charged to.

Make sure the session history you can reach covers the whole billing period. If any work ran on another machine or account, plan to collect it before the review.

Step by step

  1. List the agent sessions for the period you are billing. Include every session run for the client and note the accounts and projects each one used.
  1. Gather the cost or usage figures for those sessions. Record the model, project, and account tied to each amount so the charge can be explained to the client. Keep the same level of detail across all entries so the record reads consistently.
  1. Match each amount to a client and project. Group the usage by the client it belongs to and keep separate any work done for other clients or for the consultant's own testing.
  1. Check the plan and quota that apply to the usage. Confirm how much each session consumed, which plan the session ran under, and whether any account limit was reached during the period.
  1. Compare the session history with the reported usage. The sessions you see should line up with the amounts the tool records, so a mismatch between the two is caught early and can be investigated.
  1. Export the numbers in a form that can go on an invoice. A text or structured format another app can read makes the record easy to reuse each month instead of retyping it.
  1. Recheck the figures before the bill is sent. Missing sessions and mislabeled projects are easier to fix while the review is still in hand, and a clean record holds up better if a client questions a charge later.

Tools that can do it

AgentHydra is made by the team that publishes this site.

AgentHydra shows Claude Code, Codex and OpenCode sessions on your machine in one searchable list, updated live while they run. [1]

AgentHydra shows cost at API list prices by day, model, project and account. [1]

AgentHydra prints the same cost numbers as JSON from the command line. [1]

AgentHydra lists each Claude and Codex account with its plan and 5-hour and weekly quota, and can open, focus, quit, create and delete Claude Desktop instances. [1]

AgentHydra exposes its features as MCP tools, including whoami and usage checks so an agent knows which account it is on and how much quota is left. [1]

AgentHydra is free, with no account or subscription. [1]

AgentHydra is open source under the MIT License. [1]

The tray app needs Windows; macOS and Linux builds exist but have not been verified. [1]

On Windows, install with a one-line PowerShell script, or download a build from GitHub Releases or run from source with Bun. [1]

Other options include using the session views and billing records already in place at the consultancy, or a separate tool that records usage, after checking what it captures and how it reports cost. Compare each option against the job of turning agent history into a client bill.

Common mistakes to avoid

Reviewing only part of the history. When sessions for a client run across several accounts or machines, an incomplete list produces an incomplete bill.

Mixing clients in the same record. Label each session with its client, project, and account so usage can be billed to the right place.

Treating recorded numbers as a final invoice without checking them. When a tool reports cost in its own terms, confirm what the figure means before it reaches the client.

Ignoring plan and quota differences. Usage recorded under different plans may be priced differently, so keep the plan details with the session.

Leaving no record of the review. A history that is looked at and discarded cannot answer a later question about a charge.

Frequently asked questions

How can an AI consultant review agent history for billing?

An AI consultant can review agent history by collecting the sessions that ran for each client and comparing them with the cost or usage figures the tool records. The checks that matter are whether all sessions appear, whether each one is linked to the right client, project, and account, and whether the reported numbers cover the whole billing period. Keeping the plan details with each session helps explain how the usage was priced.

Does AgentHydra show the cost of agent sessions?

AgentHydra shows cost at API list prices by day, model, project and account. [1] It also prints the same cost numbers as JSON from the command line. [1] An AI consultant can use these figures as a starting point by checking them against the actual sessions run for a client and confirming what the numbers mean before they are put on an invoice.

Can AgentHydra separate session usage by client?

AgentHydra shows cost at API list prices by day, model, project and account. [1] Because the figures are grouped by project and account, a consultant can line them up with the sessions belonging to each client. The useful step is to confirm that the projects and accounts match the way client work is organized before the numbers are used for billing.

Is AgentHydra free to use for billing reviews?

AgentHydra is free, with no account or subscription. [1] It is open source under the MIT License. [1] The tray app needs Windows, and macOS and Linux builds exist but have not been verified. [1] An AI consultant can compare this free option with the workflow already in use by checking what each approach captures and reports.

What should be checked before using agent history for a client bill?

Check which sessions appear in the history and whether they cover the whole billing period. Confirm that each session is tied to the right client, project, and account, and that the cost figures have the same level of detail across all entries. Also check what the recorded numbers mean, since some tools report usage in their own terms rather than a billed amount, and keep the plan details that affect pricing.

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