Add Kimi K2 usage dashboard shortcut#1919
Conversation
|
Codex review: needs real behavior proof before merge. Reviewed July 6, 2026, 6:07 PM ET / 22:07 UTC. Summary Reproducibility: yes. for the PR defect: source shows Usage Dashboard opens metadata URLs directly through Review metrics: 2 noteworthy metrics.
Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Rank-up moves:
Proof guidance:
Risk before merge
Maintainer options:
Next step before merge
Maintainer decision needed
Security Review findings
Review detailsBest possible solution: Keep Kimi K2 Do we have a high-confidence way to reproduce the issue? Yes for the PR defect: source shows Usage Dashboard opens metadata URLs directly through Is this the best way to solve the issue? No as submitted; the shared metadata seam is the right implementation point only if there is a maintainer-approved browser dashboard URL. The current value is the API endpoint and lacks live proof of a usable dashboard landing. Full review comments:
Overall correctness: patch is incorrect AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against 63c69fdcc47f. Label changesLabel justifications:
Evidence reviewedWhat I checked:
Likely related people:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. How this review workflow works
Review history (6 earlier review cycles)
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9bfd6389b9
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
clawsweeper
Bot
added
rating: 🦪 silver shellfish
joeVenner
changed the title
|
@clawsweeper re-review |
|
@codex review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 038e0b0be3
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| usesAccountFallback: false, | ||
| browserCookieOrder: nil, | ||
| dashboardURL: nil, | ||
| dashboardURL: "https://kimi-k2.ai/", |
There was a problem hiding this comment.
The new menu action opens this URL directly through dashboardURL(for:), but the Kimi K2/Kimrel API docs list usage tracking at /my-credits (https://kimrel.com/my-credits). With https://kimi-k2.ai/, the “Usage Dashboard” shortcut lands on the marketing/home page instead of the credit dashboard, so users still have to navigate manually to see the balance this provider tracks.
Useful? React with 👍 / 👎.
|
@clawsweeper re-review |
|
@openclaw-mantis visual task: verify Kimi K2 shows Usage Dashboard in CodexBar and opens https://kimrel.com/ via https://kimi-k2.ai/. |
clawsweeper
Bot
added
rating: 🧂 unranked krab
|
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
|
@clawsweeper re-review |
The descriptor was updated to https://kimi-k2.ai/api/user/credits but this expectation was left at the prior https://kimi-k2.ai/ value, so the suite failed after the dashboard URL change.
The committed proof image was a 1x1 placeholder, not real evidence. Executable test output in the PR description replaces it.
|
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
1 participant
Summary
https://kimi-k2.ai/api/user/credits, the same host/path the credits fetcher pollsProof
Deterministic test run on this branch (no network, no credentials):
Open question for the maintainer — please advise
The linked URL is the authenticated API endpoint that
KimiK2UsageFetcherpolls withAuthorization: Bearer <apiKey>. The menu'sopenDashboardaction opens it in a browser viaNSWorkspacewith no auth headers, so a no-auth request returns HTTP 401 (confirmed by curl). The shortcut may still work for a user logged into kimi-k2.ai in their browser (cookie auth), but it is not a confirmed human-readable credits page.This also reverts the deliberate decision in #967 to keep
KimiK2dashboardURLnil, to avoid presenting the unofficialkimi-k2.aiendpoint as an official surface.docs/kimi-k2.mdrecommends the Moonshot/Kimi provider for the official billing surface, and an earlier Codex review suggestedhttps://kimrel.com/my-creditsas the human usage page. I could not verify the correct browser URL without a live account, so I'm flagging rather than guessing. Options:https://kimi-k2.ai/api/user/credits(works only for cookie-authenticated browser sessions).https://kimrel.com/my-credits(the human page suggested by the Codex review).dashboardURLto nil (preserves the Clarify unofficial Kimi K2 provider #967 decision — no shortcut).Codex review follow-up
The earlier review flagged a host mismatch (dashboard vs. fetcher host). The descriptor and metadata both point at
https://kimi-k2.ai/api/user/credits, matchingKimiK2UsageFetcher.creditsURL, and the metadata test was aligned to that value (it was stale athttps://kimi-k2.ai/and failing).Testing
swift test --disable-sandbox --filter 'MenuDescriptorKimiK2Tests|ProviderMetadataStatusLinkTests'(3 passed)swift buildclean