Repository navigation
chore(models): price the November 16 catalog additions - #220
Conversation
pierreraby
left a comment
There was a problem hiding this comment.
Reviewed head eaf3cc8 against 3b60d88 in an isolated worktree. The two prices match the official pricing page, including cache column order, with no additional tier or promotion for these rows. Local typecheck, pricing/models/pricing-check/cost tests, entrypoint typecheck, formatting, and full npm test with both Pi and OMP required passed against mocks. A second fresh-context read-only review found no blocking defect in this pricing change.
Upstream moved after this snapshot: the public API now lists 101 models (Flint is new), and command-code@1.89.2 adds capabilities for Qwen4-Max, Hy4 Flash and Flint. The live pricing and catalog gates therefore still require a follow-up; I will handle that separately and update the Unreleased wording before release.
One validation clarification: the host-contract and routing suites passed, but they do not contain dedicated scenarios named for these two new model IDs.
I am currently handling day-to-day maintenance solo; keeping this merge limited to the reviewed price additions. No billable inference was performed.
Sync command-code 1.89.2 capabilities and review the 101-model API snapshot. Add undated free-tier pricing for Flint and explicit model/routing and pricing-page ID regressions. Correct the Unreleased description following #220.
Summary
/provider/v1/modelsadvertised 100 models on 2026-11-16 (was 98 on 2026-11-13). Two of them had no reviewed price, so pi showed a zero estimate plus an unknown-price warning on every request that used them, and the daily catalog workflow would fail its pricing gate.Reviewed against https://commandcode.ai/docs/resources/pricing-limits. The page column order is context, input, output, cache read, cache write; a
—column means0:Qwen/Qwen4-Max/chat/completions,/responsestencent/hy4-flash/chat/completions,/responsesNeither row carries an "Available on …" plan note or a long-context tier, and the promotions table publishes no deal for them, so no
TEMPORARY_PRICINGentry is involved. The page ids areqwen-4-maxandtencent/hy4-flash.Sources and policy
id,name,context_lengthandsupported_endpoints(/chat/completions,/responses); contexts are 1,000,000 and 1,024,000 tokens.command-code@1.89.1and does not list either model. Both therefore keep the conservative text-only, non-reasoning defaults with a 65,536-token output limit until upstream publishes capabilities.Changes
Five files: two
MODEL_COSTSentries plus the verification date insrc/pricing.ts, regenerated API model-ID and official pricing fixtures (100 models, verified 2026-11-16), an explicit rate regression test for both models, and a CHANGELOGUnreleasedentry. No runtime, routing, workflow, CLI-pin or other model rates changed.Validation
npm run check:commandcode-pricingexited1withmissing-local-pricefor exactlyQwen/Qwen4-Maxandtencent/hy4-flash.npm run check:commandcode-catalog→ metadata Current atcommand-code@1.89.1(78 image, 87 reasoning, 72 efforts, 10 output limits), zero diff.npm run test:pricing15/15 PASS (including both new rates and the provenance date);npm run test:models32/32 PASS plus the metadata checker 19/19 PASS.npm run typecheck,npm run format:checkandgit diff --checkPASS.npm testPASS against real hosts, including the host-contract and endpoint-routing scenarios for both new models.Limits
command-code@1.89.1, so both models remain text-only without reasoning or effort flags even though a future CLI release may advertise more. That is catalog work for a future refresh, not part of this price update.