Repository navigation
Link provider detail to the plan usage page - #16
Merged
Merged
Conversation
Open the provider's own usage page from the detail screen when that page has a stable URL, so the panel can point at history it does not reconstruct. Co-authored-by: wjcjttl9 <wjcjttl9@gmail.com>
TiantianFlow
marked this pull request as ready for review
October 2, 2026 01:25
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
2 participants
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
The side panel already opens API-key setup pages during connect, and the footer links to this repository. It did not link to a provider's own usage page.
Provider detail now shows a Usage page link beside local history when that plan has a stable public URL. The link opens in a new tab. Plans without a known usage URL keep the detail screen unchanged.
https://chatgpt.com/codex/settings/usagehttps://claude.ai/settings/usagehttps://www.kimi.com/membership/subscriptionhttps://cursor.com/dashboard/spendinghttps://admin.mistral.ai/organization/usagehttps://www.perplexity.ai/account/usagehttps://platform.openai.com/usageGrok, the self-hosted relays, and the other API-key providers stay without a link. Their setup pages are key-creation pages, not usage history.
Test plan
pnpm exec vitest run providers/catalog.test.ts entrypoints/sidepanel/Cockpit.test.tsx i18n/catalog-contract.test.tspnpm exec tsc --noEmit