Cut your AI coding bill, not your output.
Your AI coding spend lands as one opaque number a month. Frugl reads every session, flags the tokens that bought you nothing, and shows each engineer how to get the same work done for less.
The problem
You can’t cut what you can’t see.
Most of the burn is noise: a flaky test or a stack trace gets pasted back in, the assistant retries blind, and the same error loops for thousands of tokens before anything lands. Add bloated prompts and wandering tangents across four assistants, and it all arrives as one opaque number at month’s end — with no way to say which sessions paid off and which just spun on a noisy error.
Frugl reads the whole firehose and does two things: it flags the waste it finds — naming the smallest fix that claws the budget back — and it gives each engineer concrete feedback on how to waste less next time.
How it works
From every session to the receipt.
Raw AI coding sessions in · one ranked receipt out · nothing wasted in between.
-
Your team’s sessions
Every prompt, retry and tangent — across four AI assistants.
8 engineers · 598 sessionsClaude CodeCodexGeminiCursor -
One command to upload
Redacts on-device, then uploads the anonymized sessions.
$frugl upload✓ 598 sessions · Claude Code, Codex, Gemini, Cursor✓ redacted on-device · nothing sensitive left the machine→ uploading 598 anonymized sessions… -
Frugl finds the waste
Frugl ranks the spend, flags the waste, and writes each fix.
Rank by spend Flag the waste Match to PRs Write each fix -
Your receipt & reports
A shared team dashboard, and a private report for every engineer.
01 · Find the waste
It finds the waste. Then it names the fix.
No vanity charts. Frugl ranks where the tokens went, flags what was wasted, and hands you the single change worth making this week — quantified, so cutting waste never slows the team down.
Where Acme Inc's AI spend went
Illustrative figures. Frugl is pre-launch — the dashboard reads live once your sessions are connected.
02 · Level up every engineer
Your team gets better at AI, week over week.
Finding waste once is easy; using AI better is the part that sticks. Each engineer gets a private, plainspoken review of what cost the most in their own sessions — with the one change that fixes it. No blame, no public leaderboard. Just the receipt, and how to read it next time.
- Private per-dev feedback, never a public ranking
- Specific and quantified — “do this, save that”
- Watch each fix’s savings add up, week over week
4 MCP tools unused but loaded in root context — drop them from the config so they stop loading on every call.
Six blind retries after the same failing test. Pin the test command in CLAUDE.md so it stops guessing.
Opus did featherweight edits in 18 sessions. Route quick edits to a smaller model.
What Frugl counts
Everything counted, nothing wasted.
Frugl watches the parts of AI-assisted engineering that never make it onto an invoice — the token waste that hides between the lines of every session.
-
Root-context bloat
CLAUDE.md and config files that have outgrown their usefulness — re-sent on every single call.
-
Loops & blind retries
Runs that spun in circles, and the retries that fired again after the same error never lands.
-
Tool & MCP failures
Which tools and MCP servers get called, how often they fail, and what those failures cost.
-
Skills nobody calls
Installed skills and tools that sit in context burning tokens but never actually get used.
-
Wrong-sized models
Where a heavyweight model did featherweight work, so you can right-size without losing quality.
-
Spend that shipped nothing
Sessions tied to merged PRs vs. the spend that produced no code at all — told apart at a glance.
Privacy-first
Built to be trusted with the work that matters.
Get your team’s first report.
Frugl is in private preview. Request access and we’ll send an invite to app.frugl.dev — usually within two business days. Already in? Log in and pick up where you left off.