The Reporting connector lets anyone on your team ask Claude what you are spending on Claude Code, where it goes, and what Lineman saved. Straight from Claude Desktop or Claude Code, in plain English, with no dashboard to learn.
Loaded tools · used Lineman Reporting
Here is your Lineman spend for last month:
Want me to break it down by repo, developer, or cost centre?
Finance and owners tracking the bill, managers watching where spend goes, and developers checking their own usage. Everyone asks in their own words and gets the answer scoped to what they are allowed to see.
Track the bill, the allowance, and the savings without waiting for a report.
“How much did Lineman save us last month, in tokens and in dollars?”
See where spend goes across repos and people, and how this month compares.
“Which repos used Lineman the most this week?”
Check your own usage and cost in seconds, without leaving your editor.
“How many Lineman calls did I make yesterday, and what did they cost?”
Open Claude, ask a question, get the answer. The connector pulls your live numbers (savings, budgets, who spent what) and Claude explains them. Administrators can make changes just by asking.
I will pull that up.
Loaded tools · used Lineman Reporting
Here is last month at a glance:
Want a breakdown by cost centre?
Loaded tools · used Lineman Reporting
This month by cost centre:
Loaded tools · used Lineman Reporting
Done. Growth now has a $500/mo budget with an alert at 80% ($400). I will flag it in the dashboard when it trips.
Illustrative conversation. Your answers reflect your own account and role.
Ask a question, then follow up naturally. A few starting points, grouped by what people usually want to know.
You sign in with your normal Lineman account, so Claude reads your numbers and nobody else's.
Members and auditors get read-only answers. Only administrators can change budgets and cost centres.
The connector reports on usage and savings. Your source code is never part of what it can see.
Claude Code makes the total easy to find. Run /cost in a session, or export a spend report from the admin console, and you get token usage and an estimated figure. What neither tells you is the part teams actually argue over: which repository ran up the bill, which developer, which branch, and which client or cost centre it should land on.
Lineman prices and records every call as you work and attributes it for you, so tracking Claude Code costs stops being a monthly CSV you reconcile against git history by hand. The Reporting connector puts all of it behind a question. Ask what a repo cost last week, who your heaviest users were, or whether you are on track for budget, and Claude reads the numbers back. Administrators can set a budget and an alert in the same message.
And because the Lineman plugin compresses the data-heavy calls before they reach the model, the number you are tracking is already lower. You are not just watching Claude Code costs. You are cutting them.
If you have something we haven't covered, email us and we'll get back to you.
No. The Lineman plugin compresses your files in Claude Code to lower the bill. The Reporting connector is a separate, read-first connector that answers questions about the usage and savings the plugin records. You can use either or both.
Start with Lineman and connect the Reporting assistant to ask Claude anything about your usage, savings, and budgets.
Already using Lineman? Connect the reporting assistant.