Aller au contenu

AI cost tracking

Claude Code and Codex cost tracking by project and PR

How much your team spends on Claude Code and Codex — and on what exactly: which project, pull request and period. Nythrex collects telemetry from developers’ AI coding tools, links sessions to commits and shows the cost next to what came out of it.

Why the provider’s bill is not enough

The AI provider’s console shows how much was spent and on which models. But a manager’s question is different: did this spend pay off? To answer it you need to know which session ended in a commit, which commit became a pull request and whether that reached production.

  • sessions that produced no commit look exactly like successful ones on the bill;
  • an expensive model on helper requests hides inside the total;
  • paying for the context again after a long pause is invisible without analysing the cache;
  • the split by project has to be guessed.

What arrives and what does not

AI tool telemetry data
ArrivesNever stored
time, model and token count of every requestprompt and response text
the cost the tool estimates itselfcode and file contents
session ID, account email, organizationfile names
repository URL, branch and commit of the sessiontool parameters and output

Codex adds tool arguments and output snippets to its telemetry and does not let you turn this off. Nythrex drops them on arrival, without reading or storing them. More about security.

How to connect

  1. 1

    Create a workspace and a project

    Sign up, answer three short questions — and the workspace is ready.
  2. 2

    Run the command on your machine

    The command opens a confirmation page and configures the Claude Code and Codex installations it finds: curl -fsSL https://app.nythrex.com/api/ai/connect.sh | sh
  3. 3

    Work as usual

    New sessions arrive on their own. For an exact link to the code, commits are signed with the session ID.

What you will see

  • Spend by project and person

    AI spend in any cut: project, team, person, period — and the change against the previous one.
  • The cost of every pull request

    Sessions linked to a commit are added to the cost of the change, together with CI.
  • Unlinked AI on its own line

    Sessions with no commit neither vanish nor get spread around: they are shown on their own line.
  • AI recommendations

    Sessions with no commit, an expensive model on subagents, cache rewrites. All rules.
A member sees only their own cost; colleagues’ data by name is visible only to the workspace owner and admins.

Questions fréquentes

Does Nythrex see our prompts?

No. It receives the time, model, token count, cost, session ID, account, repository URL, branch and commit. Prompt and response text, code, file contents and file names are not stored.

What if we are on a subscription and do not pay per token?

Then there is no actual price per request. Nythrex prices the same tokens from the price list and clearly calls the amount an estimate, so it is never mistaken for an invoice.

Are GitHub Copilot and Cursor supported?

Claude Code and Codex are supported today. GitHub Copilot and Cursor are among the sources in preparation; we show them as “coming soon” until they are available.

How do we connect the whole team?

Each machine connects with one command, confirmed by a member of the workspace. For a team there is one settings block that can be rolled out centrally.

How long does an AI tool’s access last?

A device token is valid for 90 days and checks workspace membership on every upload. A member removed from the workspace loses access immediately.

    Cessez de deviner.
    Commencez à voir.

    Sans carte et sans abonnement : les offres payantes ne sont pas encore lancées.

    Créer un compteSans carte ni abonnement