Skip to content

Add Kimi models.dev pricing lookup - #2374

Closed
joeVenner wants to merge 8 commits into
steipete:mainfrom
joeVenner:codex/modelsdev-kimi-moonshot
Closed

joeVenner wants to merge 8 commits into
steipete:mainfrom
joeVenner:codex/modelsdev-kimi-moonshot

Conversation

@joeVenner

@joeVenner joeVenner commented Jul 21, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Add an additive provider-aware models.dev lookup seam for CodexBar providers.
  • Map kimi to the kimi-for-coding catalog and moonshot to the paid Moonshot/Kimi API catalogs.
  • Normalize the documented Kimi k3[1m] alias to the k3 catalog row, wire Kimi/Moonshot pricing into Pi session runtime cost, and expose both providers through codexbar cost.

Proof

  • Previous-context check: PR Add GPT-5.6 Sol/Terra/Luna Codex pricing #2023 added GPT-5.6 bundled pricing, PR Fix: Refresh pricing for unknown models #2018 added unknown-model refresh behavior, and PR Improve China Kimi/GLM routes: Coding Plan 5h, Kimi Monthly, clearer labels #2351 is Kimi/GLM quota routing rather than these model IDs.
  • Absence check against current base returned no matches:
    git grep -n -E "kimi-k3|kimi-k2\.7-code|kimi-for-coding-highspeed" origin/main -- Sources Tests docs
  • Source catalog check from https://models.dev/api.json showed:
    • kimi-for-coding: k3 / Kimi K3 / input 0 / output 0 / cache_read 0 / cache_write 0 / context 1048576
    • kimi-for-coding: kimi-for-coding / Kimi K2.7 Code / input 0 / output 0 / context 262144
    • kimi-for-coding: kimi-for-coding-highspeed / Kimi For Coding HighSpeed / input 0 / output 0 / context 262144
    • moonshotai: kimi-k2.7-code / Kimi K2.7 Code / input 0.95 / output 4 / cache_read 0.19 / context 262144
    • moonshotai: kimi-k2.7-code-highspeed / Kimi K2.7 Code HighSpeed / input 1.9 / output 8 / cache_read 0.38 / context 262144
    • moonshotai: kimi-k3 / Kimi K3 / input 3 / output 15 / cache_read 0.3 / context 1048576
  • Official docs cross-check: Kimi API docs list Kimi K3, Kimi K2.7 Code, Kimi K2.6, and Moonshot V1 on the pricing/model pages (https://platform.kimi.ai/docs/pricing/chat, https://platform.kimi.ai/docs/models).
  • Helper regression now verifies CostUsagePricing.modelsDevPricing(provider: .kimi, model: "k3[1m]") resolves with normalizedModelID == "k3".
  • Runtime regression test writes cached models.dev fixture data, then verifies PiSessionCostScanner.loadDailyReport computes costs for Pi JSONL rows:
    • kimi / k3[1m]: 160 tokens, cost 0.000252, proving the alias reaches the k3 catalog row
    • moonshotai / kimi-k3: 160 tokens, cost 0.001053
  • Built CLI proof used an isolated temp home with a synthetic .pi/agent/sessions/2026-07-28T10-00-00-000Z_kimi-proof.jsonl containing only two assistant rows. No real account files, Keychain, or browser cookies were read. Command shape:
    HOME=[temp] CFFIXED_USER_HOME=[temp] XDG_CONFIG_HOME=[temp]/.config XDG_CACHE_HOME=[temp]/.cache .build/debug/CodexBarCLI cost --provider kimi --format json --pretty --refresh
    Output excerpt:
    {
      "provider" : "kimi",
      "source" : "local",
      "sessionTokens" : 160000,
      "sessionCostUSD" : 0,
      "daily" : [{
        "date" : "2026-07-28",
        "inputTokens" : 100000,
        "cacheReadTokens" : 10000,
        "outputTokens" : 50000,
        "totalTokens" : 160000,
        "totalCost" : 0,
        "modelBreakdowns" : [{ "modelName" : "k3[1m]", "totalTokens" : 160000, "cost" : 0 }]
      }]
    }
    Public models.dev currently publishes zero prices for kimi-for-coding/k3, so the proof expectation is row inclusion plus zero-priced catalog resolution for kimi.
  • Built CLI proof for the paid Moonshot catalog row used the same isolated Pi fixture:
    HOME=[temp] CFFIXED_USER_HOME=[temp] XDG_CONFIG_HOME=[temp]/.config XDG_CACHE_HOME=[temp]/.cache .build/debug/CodexBarCLI cost --provider moonshot --format json --pretty --refresh
    Output excerpt:
    {
      "provider" : "moonshot",
      "source" : "local",
      "sessionTokens" : 160000,
      "sessionCostUSD" : 1.053,
      "daily" : [{
        "date" : "2026-07-28",
        "inputTokens" : 100000,
        "cacheReadTokens" : 10000,
        "outputTokens" : 50000,
        "totalTokens" : 160000,
        "totalCost" : 1.053,
        "modelBreakdowns" : [{ "modelName" : "kimi-k3", "totalTokens" : 160000, "cost" : 1.053 }]
      }]
    }

Verification

  • CLANG_MODULE_CACHE_PATH=/private/tmp/codexbar-clang-cache swift test --disable-sandbox --scratch-path /Users/mosaab/Documents/Projects/CodexBar/.build --filter PiSessionCostScannerTests: 19 tests passed.
  • CLANG_MODULE_CACHE_PATH=/private/tmp/codexbar-clang-cache swift test --disable-sandbox --scratch-path /Users/mosaab/Documents/Projects/CodexBar/.build --filter 'provider lookup resolves current Kimi and Moonshot models': 1 test passed.
  • git diff --check: clean.
  • make check completed generated parser hash, package/docs/locales checks, SwiftFormat lint mode, and SwiftLint strict with 0 violations, then exited on the sandbox-only macOS plist cache write permission error after lint shutdown.

No live provider probes, browser-cookie imports, or Keychain reads were run.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b08f5536f9

ℹ️ 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".

Comment thread Sources/CodexBarCore/Vendored/CostUsage/CostUsagePricing.swift Outdated
@joeVenner

Copy link
Copy Markdown
Contributor Author

@clawsweeper review

@clawsweeper

clawsweeper Bot commented Jul 27, 2026 •

Copy link
Copy Markdown

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

Re-review progress:

@clawsweeper clawsweeper Bot added rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. P2 Normal priority bug or improvement with limited blast radius. merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. labels Jul 27, 2026
@clawsweeper

clawsweeper Bot commented Jul 27, 2026 •

Copy link
Copy Markdown

Codex review: needs changes before merge. Reviewed August 23, 2026, 4:45 PM ET / 20:45 UTC.

ClawSweeper review

What this changes

Adds models.dev pricing lookup and codexbar cost support for Kimi and Moonshot Pi session logs.

Regression provenance

Possible regression — suspected (reviewed change). No predecessor PR is attributed.

Merge readiness

⛔ Blocked by patch quality or review findings - 8 items remain

Keep open: current main and v0.54.1 still lack Kimi/Moonshot Pi pricing, but this merge-dirty branch regresses Claude/Vertex filtering, ignores Moonshot region pricing, and includes substantial unrelated artifacts.

Priority: P1
Reviewed head: c3f0e5656bd0941d831f14cd8957c294fee93c98

Review scores

Measure Result What it means
Overall readiness 🧂 unranked krab (1/6) The direct scanner proof is strong, but existing provider filtering and region-aware pricing are not safe at this head.
Proof confidence 🦞 diamond lobster (5/6) Sufficient (terminal): The PR body provides after-fix terminal output from isolated synthetic Pi logs for Kimi and Moonshot, without real account or credential access.
Patch quality 🧂 unranked krab (1/6) 3 actionable review findings remain.

Verification

Check Result Evidence
Real behavior Verified Sufficient (terminal): The PR body provides after-fix terminal output from isolated synthetic Pi logs for Kimi and Moonshot, without real account or credential access.
Evidence reviewed 4 items Current main lacks the requested providers: The current main scanner accepts only Codex and Claude Pi reports; the latest release v0.54.1 contains the same commit ancestor.
Existing Claude/Vertex filters are absent from the branch: Current main assigns vertexAIOnly or excludeVertexAI; the PR-head refresh setup has no equivalent assignments.
Moonshot pricing disregards configured region: Moonshot defines distinct international and China API regions, but the lookup always tries moonshotai before moonshotai-cn without receiving a region.
Findings 3 actionable findings [P1] Restore Claude and Vertex transcript filtering
[P2] Select Moonshot pricing from the configured region
[P2] Remove unrelated local review artifacts
Security None None.

Live Verification

Command: HOME=/tmp/codexbar-proof CFFIXED_USER_HOME=/tmp/codexbar-proof XDG_CONFIG_HOME=/tmp/codexbar-proof/.config XDG_CACHE_HOME=/tmp/codexbar-proof/.cache .build/debug/CodexBarCLI cost --provider kimi --format json --pretty --refresh

Result: FAIL (failed) — execution before step 1 run: sh -lc pnpm install --ignore-scripts --frozen-lockfile failed: ! Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-11.23.0.tgz

sh -lc pnpm install --ignore-scripts --frozen-lockfile failed: ! Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-11.23.0.tgz

Assertions:

  • FAIL expect_output: "provider" : "kimi"
  • FAIL expect_output: "modelBreakdowns"

How this fits together

CodexBar scans local session logs, combines token counts with cached models.dev pricing, and presents daily cost reports through the CLI and menu-bar app.

flowchart LR
A[Local Pi session logs] --> B[Cost usage fetcher]
B --> C[Provider scan selection]
D[models.dev pricing cache] --> E[Provider price lookup]
C --> E
E --> F[Daily cost report]
F --> G[CLI and app displays]
Loading

Before merge

  • Restore Claude and Vertex transcript filtering (P1) - The branch drops current main’s .excludeVertexAI and .vertexAIOnly assignments. Normal Claude scans can count Vertex transcripts, while Vertex loses its provider-specific filter. Restore them and add a mixed-log regression.
  • Select Moonshot pricing from the configured region (P2) - Moonshot has separate international and China endpoints, but this lookup always selects moonshotai before moonshotai-cn and has no region input. China-configured users can receive international prices when model IDs overlap.
  • Remove unrelated local review artifacts (P2) - The patch includes .claude/tmp reports, full patches, shell scripts, and a watch artifact unrelated to Kimi/Moonshot pricing. Remove them so the PR can be reviewed and rebased as a focused change.
  • Resolve merge risk (P1) - Merging as-is can misattribute Claude and Vertex transcripts and can price China-region Moonshot usage from the international catalog.
  • Complete next step (P2) - The blockers have narrow source and test locations, so a focused repair can preserve the intended pricing feature without a product decision.
  • Improve patch quality - Restore the current-main filters and add a mixed Claude/Vertex-log regression.
  • Improve patch quality - Pass the configured Moonshot region through pricing lookup and test divergent catalog rows.
  • Improve patch quality - Rebase a clean branch without .claude/tmp or watch artifacts.

Findings

  • [P1] Restore Claude and Vertex transcript filtering — Sources/CodexBarCore/CostUsageFetcher.swift:1184-1191
  • [P2] Select Moonshot pricing from the configured region — Sources/CodexBarCore/Vendored/CostUsage/CostUsagePricing.swift:884-885
  • [P2] Remove unrelated local review artifacts — .claude/tmp/china.patch:1
Agent review details

Security

None.

Review metrics

Metric Value Why it matters
Patch scope 22 files, +2,980/-424; 13 unrelated artifact files add 2,171 lines The artifacts obscure a focused provider-pricing change and make the merge conflict harder to review safely.

Merge-risk options

Maintainer options:

  1. Repair before merge (recommended)
    Restore Claude/Vertex filtering, choose Moonshot pricing from the configured region, remove artifacts, and rebase onto current main.
  2. Pause the stale branch
    Pause or close the branch if a clean rebase cannot retain only the Kimi/Moonshot pricing work.
Copy recommended automerge instruction
@clawsweeper automerge

Special instructions:
Restore Claude/Vertex filters, select Moonshot pricing by configured region, remove unrelated artifacts, rebase onto current main, and add regressions.

Technical review

Best possible solution:

Rebase a narrow Kimi/Moonshot patch that preserves existing scan filters, selects Moonshot pricing by configured region, and excludes all review artifacts.

Do we have a high-confidence way to reproduce the issue?

Yes for the source-level regressions: current main’s filter assignments are absent at the PR head, and Moonshot lookup always prioritizes the international catalog despite separate region settings.

Is this the best way to solve the issue?

No; the provider-aware models.dev lookup fits the existing architecture, but it must preserve filtering and carry Moonshot region selection to be correct.

Full review comments:

  • [P1] Restore Claude and Vertex transcript filtering — Sources/CodexBarCore/CostUsageFetcher.swift:1184-1191
    The branch drops current main’s .excludeVertexAI and .vertexAIOnly assignments. Normal Claude scans can count Vertex transcripts, while Vertex loses its provider-specific filter. Restore them and add a mixed-log regression.
    Confidence: 0.99
  • [P2] Select Moonshot pricing from the configured region — Sources/CodexBarCore/Vendored/CostUsage/CostUsagePricing.swift:884-885
    Moonshot has separate international and China endpoints, but this lookup always selects moonshotai before moonshotai-cn and has no region input. China-configured users can receive international prices when model IDs overlap.
    Confidence: 0.96
  • [P2] Remove unrelated local review artifacts — .claude/tmp/china.patch:1
    The patch includes .claude/tmp reports, full patches, shell scripts, and a watch artifact unrelated to Kimi/Moonshot pricing. Remove them so the PR can be reviewed and rebased as a focused change.
    Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.99

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 63dc1cd520f0.

Labels

Label changes:

  • add merge-risk: 🚨 auth-provider: Moonshot's configured provider region is not honored for pricing lookup.

Label justifications:

  • P1: The branch regresses established Claude/Vertex transcript filtering.
  • merge-risk: 🚨 compatibility: Existing provider transcript attribution and cost reports can change on upgrade.
  • merge-risk: 🚨 auth-provider: Moonshot's configured provider region is not honored for pricing lookup.
  • rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🦞 diamond lobster and patch quality is 🧂 unranked krab.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Sufficient (terminal): The PR body provides after-fix terminal output from isolated synthetic Pi logs for Kimi and Moonshot, without real account or credential access.
  • proof: sufficient: Contributor real behavior proof is sufficient. The PR body provides after-fix terminal output from isolated synthetic Pi logs for Kimi and Moonshot, without real account or credential access.

Evidence

Acceptance criteria:

  • [P1] swift test --filter PiSessionCostScannerTests.
  • [P1] swift test --filter ModelsDevPricingTests.
  • [P1] swift test --filter CostUsageFetcherTests.
  • [P1] make check.

What I checked:

Likely related people:

  • steipete: Current-main blame attributes the Claude/Vertex filter and Moonshot-region surface to Peter Steinberger, and the owner set the pricing-series landing order in discussion. (role: recent area contributor; confidence: high; commits: d6d281e898a0; files: Sources/CodexBarCore/CostUsageFetcher.swift, Sources/CodexBarCore/Providers/Moonshot/MoonshotRegion.swift)

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
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.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (31 earlier review cycles; latest 8 shown)
  • reviewed 2026-08-09T18:16:00.862Z sha dbe62e2 :: needs changes before merge. :: [P1] Restore Claude and Vertex provider filtering | [P1] Synchronize provider architecture gates | [P2] Route Moonshot pricing by configured region
  • reviewed 2026-08-09T19:50:33.594Z sha dbe62e2 :: needs changes before merge. :: [P1] Restore Claude’s Vertex-log filter | [P2] Select Moonshot pricing by configured region
  • reviewed 2026-08-09T21:13:07.296Z sha dbe62e2 :: needs changes before merge. :: [P1] Restore Claude and Vertex transcript filtering | [P2] Select Moonshot pricing by configured region
  • reviewed 2026-08-09T22:26:03.776Z sha b3d0a09 :: needs changes before merge. :: [P1] Preserve Claude’s Vertex-log exclusion | [P2] Route Moonshot pricing by selected region
  • reviewed 2026-08-12T09:14:15.375Z sha b3d0a09 :: needs changes before merge. :: [P1] Restore Claude’s Vertex-log exclusion | [P2] Select Moonshot pricing by configured region
  • reviewed 2026-08-15T15:26:51.264Z sha 5b56d8a :: needs changes before merge. :: [P1] Restore Claude’s Vertex-log exclusion | [P2] Select Moonshot pricing by configured region
  • reviewed 2026-08-15T16:23:21.978Z sha 6160fb5 :: needs changes before merge. :: [P1] Restore Claude and Vertex transcript filtering | [P2] Select Moonshot pricing from the configured region
  • reviewed 2026-08-16T18:19:08.114Z sha c3f0e56 :: needs changes before merge. :: [P1] Restore Claude and Vertex transcript filtering | [P2] Select Moonshot pricing from the configured region | [P2] Remove unrelated local review artifacts

@joeVenner

Copy link
Copy Markdown
Contributor Author

@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Jul 28, 2026

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Command router queued. I will update this comment with the next step.

@joeVenner

Copy link
Copy Markdown
Contributor Author

@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Jul 28, 2026

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Command router queued. I will update this comment with the next step.

@clawsweeper clawsweeper Bot added proof: sufficient Contributor real behavior proof is sufficient. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. and removed rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels Jul 28, 2026
@joeVenner
joeVenner force-pushed the codex/modelsdev-kimi-moonshot branch from 6012689 to e8e0aa5 Compare July 30, 2026 11:39
@joeVenner

Copy link
Copy Markdown
Contributor Author

@clawsweeper re-review

@clawsweeper

clawsweeper Bot commented Jul 30, 2026 •

Copy link
Copy Markdown

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: when the review finishes, ClawSweeper will create the durable review comment if needed or update the existing comment in place.

Re-review progress:

@clawsweeper clawsweeper Bot added rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. and removed rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. labels Aug 4, 2026
@clawsweeper clawsweeper Bot added the merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. label Aug 6, 2026
@joeVenner
joeVenner force-pushed the codex/modelsdev-kimi-moonshot branch 2 times, most recently from 1047188 to dc128b0 Compare August 6, 2026 20:36
@clawsweeper clawsweeper Bot added merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. merge-risk: 🚨 automation 🚨 Merging this PR could break CI, automerge, proof capture, label sync, or automation. and removed merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. merge-risk: 🚨 automation 🚨 Merging this PR could break CI, automerge, proof capture, label sync, or automation. labels Aug 6, 2026
@joeVenner
joeVenner force-pushed the codex/modelsdev-kimi-moonshot branch from dc128b0 to dbe62e2 Compare August 9, 2026 14:28
@joeVenner

Copy link
Copy Markdown
Contributor Author

@steipete — this PR has been rebased onto latest main and is ready for review. Thanks!

@joeVenner
joeVenner force-pushed the codex/modelsdev-kimi-moonshot branch 2 times, most recently from 5b56d8a to 6160fb5 Compare August 15, 2026 16:18
@joeVenner
joeVenner force-pushed the codex/modelsdev-kimi-moonshot branch from 6160fb5 to c3f0e56 Compare August 16, 2026 18:14
@clawsweeper clawsweeper Bot added P1 Urgent regression or broken agent/channel workflow affecting real users now. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. and removed P2 Normal priority bug or improvement with limited blast radius. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. labels Aug 16, 2026
@clawsweeper clawsweeper Bot added the merge-risk: 🚨 auth-provider 🚨 Merging this PR could break OAuth, tokens, provider routing, model choice, or credentials. label Aug 23, 2026
@steipete

Copy link
Copy Markdown
Owner

Thanks @joeVenner. The Kimi context alias portion is already handled by #3259, including a synthetic Pi/Anthropic transcript regression. Direct Kimi and Moonshot Pi backends still need implementation. The submitted patch maps both Moonshot regions to one provider before trying the international catalog first, losing the recorded regional billing route. I recommend closing this implementation in favor of a scoped rewrite that preserves provider identity and integrates with #3246’s standalone Pi accounting. This is partial supersession, not a claim that the complete request is supported.

@steipete steipete closed this Sep 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-risk: 🚨 auth-provider 🚨 Merging this PR could break OAuth, tokens, provider routing, model choice, or credentials. merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. P1 Urgent regression or broken agent/channel workflow affecting real users now. proof: sufficient Contributor real behavior proof is sufficient. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants