Feature proposals from a power user (15+ projects, 170+ sessions/month)

[sterngold]

First — great tool. Installed via npx, zero friction, immediately useful on a 15-project setup running 170+ sessions/month across Opus and Sonnet. Starred.

Here are things I'd find valuable as a heavy user:

1. Per-project drill-down

The project breakdown shows cost + session count. I'd love codeburn report --project "My/projects" to see the full dashboard (activity type, model split, tools, one-shot rate) scoped to just that project. When one project dominates spend (mine is 88%), the aggregate view hides what's happening in smaller ones.

2. Cost-per-session metric

Average cost per session alongside the project breakdown. A $200/day number is less actionable than knowing 3 sessions averaged $60 while the rest averaged $5.

3. Date range filtering on report

codeburn report --from 2026-04-07 --to 2026-04-10. Related to #5 (billing period) but more general. The export command could benefit from this too.

4. Model efficiency comparison

For users who route between Opus/Sonnet intentionally: one-shot rate broken down by model, not just by activity. If Sonnet's one-shot rate on coding is 90% vs Opus at 93%, that's a meaningful routing decision.

5. Session outlier detection

Flag sessions costing >2x the project average. A simple "top 5 most expensive sessions" with timestamp + project + dominant activity helps spot what went wrong (or right).

6. --json flag on report

The TUI is great for human eyes, but piping structured output to dashboards, scripts, or notes would extend the value significantly.

---

Happy to test any of these. Running macOS 26, Claude Code on Opus 4.6 primarily, 170 sessions/month with submodules and multiple MCP servers.

[mallek]

Added --project and --exclude on this PR to help address your number 1
#52

[mallek]

Added --format json to address your number 6
#53

[AgentSeal]

Hi @sterngold, circling back with status. Four of your six proposals shipped in 0.6.0 / 0.6.1.

Shipped

1. Per-project drill-down. --project <name> and --exclude <name> on report, today, month, status, and export. Shipped in 0.6.1 (PR #52 by @mallek).

2. Cost-per-session metric. avg/s column in the By Project panel. Shipped in 0.6.0 (PR #51 by @lfl1337).

5. Top expensive sessions. Top Sessions panel in the dashboard shows the 5 most expensive sessions across all projects with date, project, cost, and call count. Shipped in 0.6.0 (PR #51). Dominant-activity per session is not surfaced yet.

6. --json on report. codeburn report --format json shipped in 0.6.1 (PR #53 by @mallek). Same flag on today, month, and status.

Still open

3. Custom --from/--to date range. Issue #5 covers the billing-cycle case. A generic date range on report/export is a separate small add.

4. Model efficiency comparison. One-shot rate is currently tracked by activity category only. Adding the per-model dimension is on the list.

5b. Outlier detection. Sessions costing >2x the project average. Complements the Top Sessions panel but not done yet.

Leaving this issue open for items 3, 4, and 5b. Thanks for the thoughtful write-up.

[sterngold]

Hey @AgentSeal and @mallek — thank you. Four out of six in a single release cycle is genuinely impressive. Per-project drill-down and cost-per-session are exactly what I needed most. Looking forward to date ranges and model comparison when they land. Great project.