Quiet routine pricing warnings + menubar recovery from stuck-loading#266
Open
Quiet routine pricing warnings + menubar recovery from stuck-loading#266
Conversation
CLI:
- Default `codeburn` invocation no longer prints "no pricing data for model"
warnings on every run. Greeting a fresh user with three lines of stderr
before the dashboard even draws looked like the tool was broken on first
launch. The warning now requires --verbose, and the suppressed pricing
miss still results in $0 cost (correct for unmapped models).
- Local-model heuristic skips the warning entirely for Ollama tags
(`qwen3.6:35b-a3b-bf16`), GGUF/quantized fingerprints, and similar names
that will never have public pricing. The "update codeburn" hint was
actively misleading there.
- When the warning does fire (with --verbose), it points users at
`codeburn model-alias <model> <known-model>` as the actual escape hatch
alongside the package update suggestion.
Menubar:
- Replace perpetual "Loading…" spinner with a FetchErrorOverlay when the
per-key fetch fails and the cache is empty. User sees the error and a
Retry button instead of an infinite hang.
- Add diagnostic breadcrumbs (NSLog, invisible to normal users — Console.app
/ `log stream --process CodeBurnMenubar` only) for the four states that
produce a stuck loading overlay:
- subprocess timeout after 45s
- fetch result dropped due to Task cancellation (rapid tab switch)
- fetch result dropped due to mid-fetch calendar rollover
- retry attempt where the last successful fetch is >2 min stale
- Track lastSuccessByKey separately from cache freshness so the staleness
diagnostic survives day-rollover cache wipes.
When the 30s CLI tick updated `projects` while the user was reading the model comparison results, the projects-watching effect always fired setLoadTrigger, which flipped phase to 'loading' and re-ran the slow scanSelfCorrections walk over every provider's session directory. The user lost their scroll position and saw a loading flash mid-read. Recompute the comparison rows in place when: - the user is already on the results phase, AND - both picked models still exist in the new aggregate. Skip the corrections rescan on these in-place refreshes — corrections drift slowly enough that holding the previous value until the user re-enters compare is acceptable, and the rescan is the slow part of the load. Initial selection and post-selection load still run the full pipeline.
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
1 participant
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.
Two issues observed by the user during the 0.9.7 dogfood:
codeburninvocation — greeting fresh users with three stderr lines before the dashboard drew. Looked like the tool was broken on first launch.CLI
codeburnis silent on the unknown-model warning. Opt-in via--verbose.qwen3.6:35b-a3b-bf16), GGUF / quantized fingerprints (*-bf16,*-q4_K_M, etc.) — those will never have public pricing and the "update codeburn" hint was actively misleading.codeburn model-alias <model> <known-model>as the actual escape hatch alongside the package-update suggestion.Verified:
Menubar
User-facing:
FetchErrorOverlaywith the actual error message and a Retry button replaces the perpetual loading spinner when a per-key fetch fails and the cache is empty.Diagnostic-only (NSLog → unified log, invisible to users; only visible via
Console.appfilter orlog stream --process CodeBurnMenubar):CLI subprocess timed out after 45s for status --format menubar-json --no-optimize --provider claude — terminatingfetch for today/claude cancelled before result was applieddropping fetch result for today/claude — calendar rolled mid-fetchrefresh attempt for stale key today/claude — last success was 145s agoTracks
lastSuccessByKeyseparately from cache freshness so staleness diagnostics survive day-rollover cache wipes.Notes
Test plan
npm test— 555/555swift build— cleancodeburn statusproduces zero stderr (default), warns under--verbose