feat(api): enrich provider.list with usage freshness and recent token signals#18439
Open
LucasSantana-Dev wants to merge 1 commit intoanomalyco:devfrom
Open
Conversation
github-actions
bot
added
the
needs:compliance
LucasSantana-Dev
changed the title
github-actions
bot
removed
the
needs:compliance
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
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.
Issue for this PR
Closes #9281
Type of change
What does this PR do?
This extends
provider.listwith server-derived usage freshness and recent token signals so clients can render provider usage state without duplicating inference logic.Added fields per provider:
usage.state:fresh | stale | missingusage.observedAtusage.ageMinutesusage.recentInputTokensusage.recentOutputTokensWhy this works: values are computed from recent assistant message usage on the server, so all clients consume one canonical classification path.
How did you verify your code works?
cd packages/opencode && bun run typecheckcd packages/opencode && bun test test/provider/usage.test.tsScreenshots / recordings
Not a UI change.
Checklist