Add unpriced filter to models report - #985
Open
kocaemre wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Related to #969.
The TUI warning for unpriced models points users at
codeburn model-alias, but the detailed model list is still hard to reach/copy from the dashboard.codeburn modelsis already the plain-stdout escape hatch, so this adds a focused filter for the affected rows.What
codeburn models --unpriced.0.findUnpricedModelslogic so local/free/aliased/overridden models are treated the same as the dashboard warning.Validation
npx vitest run tests/models-report.test.tsnpm run build:clinode dist/cli.js models --unpriced --from 2026-05-09 --to 2026-05-09 --provider claude --format jsonNote
I also tried
npm test -- tests/models-report.test.ts, but the script ignores the positional file argument and ran the broad suite. That broad run failed in unrelated cache/history CLI tests due the local environment picking up existing usage data; the targeted suite above passes.