Usage
Provider, model, tokens, time, cost source, and a unique call ID.
Ganox tracks proxy calls as they happen and imports completed Claude and Codex sessions. It groups the calls by project and explains each match. Connect Regrok if you also want plan and revision details. You do not have to tag every call.
It combines the usage record with a small set of details from the proxy or your local Claude and Codex history.
Provider, model, tokens, time, cost source, and a unique call ID.
Working folder, repository, tools used, files changed, and the topic of the work.
Plans and revisions from a connected planning tool. If no plan matches, Ganox suggests a plan name.
Projects shows where AI usage and cost went. Planning manages the tools Ganox uses to understand each project.
Compare projects, sort by recent activity or usage, see the types of work, and correct individual calls.
Connect Regrok and load its plans and revisions. More planning tools can be added through connectors.
Ganox can build the project report from usage and session details first. You can connect or create a plan later.
Ganox keeps the reason for the match, its confidence, the software version that made it, and any later corrections. Advertising systems never receive project names, prompts, responses, or session content.
Low-confidence and unmatched calls stay available for review instead of being hidden in a total.
Ganox does not mix a provider bill, a share of a subscription, an API price estimate, and an unknown cost.
Usage and session details are enough to start. Connecting Regrok adds plan and revision details automatically.