fix(anthropic): tolerate usage API metadata fields (limits/spend)#90
Open
yesme wants to merge 1 commit into
Open
fix(anthropic): tolerate usage API metadata fields (limits/spend)#90yesme wants to merge 1 commit into
yesme wants to merge 1 commit into
Conversation
Anthropic /api/oauth/usage now returns top-level companion fields such as limits (array), spend (unrelated object), and booleans alongside quota buckets. Decoding the whole payload as map[string]*AnthropicQuotaEntry failed with: cannot unmarshal array into Go value of type api.AnthropicQuotaEntry Add a custom UnmarshalJSON that keeps null/object quota entries and ignores non-quota metadata. Enhances onllm-dev#84 by also dropping non-quota objects (spend) and skipping per-key decode errors so one bad companion field cannot take down the entire Anthropic poll. Fixes onllm-dev#82. Related: onllm-dev#84.
hiyukoim
added a commit
to hiyukoim/onWatch
that referenced
this pull request
Jul 20, 2026
Anthropic's /api/oauth/usage now returns companion top-level fields (limits array, spend object, booleans) that broke decoding into map[string]*AnthropicQuotaEntry, taking down all Anthropic quota polling and leaving the dashboard empty even after reload. Port upstream fix from onllm-dev#90 (confirmed against live payloads in onllm-dev#82): custom UnmarshalJSON keeps quota-shaped objects, preserves null inactive buckets, and ignores non-quota metadata. Also treat a root-level empty array body as zero quotas (onllm-dev#87). Co-authored-by: Yuko <hiyukoim@users.noreply.github.com>
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.
Summary
Fixes Anthropic OAuth usage polling when
/api/oauth/usageincludes top-level metadata fields such aslimits(array),spend(unrelated object), and booleans.This is an enhanced take on #84 (same root cause / same minimal approach), with two robustness improvements observed against a live mid-2026 usage payload.
Fixes #82.
Related: #84.
Root cause
AnthropicQuotaResponsewasmap[string]*AnthropicQuotaEntry. Anthropic now returns companion top-level fields;limitsis an array, so the whole decode fails with:Auth/token refresh is fine — only response-schema decoding breaks.
Changes
UnmarshalJSONforAnthropicQuotaResponsenullinactive bucketslimits[], booleans, …)AnthropicQuotaEntryfields (e.g.spend), instead of leaving empty entries in the mapTest plan
go test ./internal/api -count=1 -run 'Anthropic|ParseAnthropic'onllm-dev/onWatch@mainand contains only this fix (single commit)