fix(usage): explain unavailable provider limits - #24
Merged
Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
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.
The Limits view could show a failed usage read for a Codex account that was never signed in, and describe unavailable Claude token or cloud-backend limits as a missing subscription.
Omit the redundant Codex warning while preserving errors for signed-in accounts. Use the same Claude probe’s account metadata to explain unavailable limits, without changing any returned usage windows or authentication state. Existing shared notice rendering carries the messages to web, desktop, and mobile over local and remote connections; other providers are unchanged.
Validation: 64 focused provider and usage tests passed, server typecheck passed, targeted lint/formatting passed. Includes regression coverage for both Claude probe paths, token and cloud-backend notices, signed-out Codex, API-key accounts, and real usage-read failures.
Model: GPT-6 Astra. Harness: Codex.