Repository navigation
feat: --usage-json prints the usage read for scripts - #23
Merged
Merged
Conversation
shayan-ys
marked this pull request as ready for review
October 30, 2026 04:32
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.
Adds
devdash --usage-json: one usage read as JSON, then exit.usage --jsonreport, plus OpenRouter and Nous as today.stale. If the read fails, the last good read is printed, all marked stale.pacein points (the number the pace icon uses).Why: the agent-brain router (
brain route) skips a provider near its quota. It reads this instead of copying devdash's carry-over and pace logic.Tests: two new unit tests (pace with stale carry-over; failure fallback).
pytest: 118 passed. Randevdash --usage-jsonagainst the live omp profile.🤖 Generated with Claude Code