feat(dev): add a demo mode with synthetic history for real-app captures - #9
Merged
Merged
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
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.
Development builds launched with
TOKENGAUGE_DEMO=1show synthetic Claude and Codex data: a seeded history database in the temporary directory feeds the panel, the history views, pace and every Stats card through the normal code paths. The demo store never refreshes live usage, keeps its preferences in a separate defaults suite and skips update checks and the recovery prompt. Distribution builds ignore the variable.DemoDataseeds quota samples, per-model tokens, reasoning effort, skills and turns.UsageStoregainshistoryURLandliveReadsEnabled; the panel and history models read from the store's history URL.