Skip to content

v5.3.1 — gpt-6.1-sol Codex catalog entry

Latest

Choose a tag to compare

@shaomingbo shaomingbo released this 30 Sep 17:39
· 0 commits to main since this release

gpt-6.1-sol Codex catalog entry

Scope: the openai-codex native capability (ChatGPT subscription). No pi-ai bump — the pinned 0.84.4 protocol template stays.

Highlights

  • Verified Codex facts for gpt-6.1-sol (upstream @earendil-works/pi-ai@0.99.1, tarball SHA1 2945bf014fbb314bd37b919e83317560e0a8fa1d, matching the npm registry dist metadata): contextWindow=272000, maxTokens=128000, text+image, and the effort mapping off→null — the off level stays offered with an absent wire value, unlike the literal none the 0.87.1 catalog used for gpt-6-sol — plus minimal→low and the unchanged low/medium/high/xhigh/max. The public API's 1050000 context is deliberately not used.
  • Runtime serves the id through the pinned-template custom-model merge: the verified-id list joins the pinned catalog so models() and resolveModel() serve one set of facts; the openai-codex route defaults include its DSH profile, so absent Settings lists materialize it; CODEX_CATALOG_REVISION bumps to codex-native-catalog/2026-10-01.1 so pending models.preview bindings rebind and models.apply keeps its digest/conflict discipline.

Install

npx --yes --ignore-scripts github:shaomingbo/dsh-token-usage#v5.3.1

Verified / not verified

Verified in isolation (independent v5.3.0 working copy; TDD red→green; full suite 423 tests / 416 pass / 0 fail / 7 optional skips, identical to the v5.3.0 baseline; npm run check, npm pack --dry-run, git diff --check pass; the upstream verification record binds the 0.99.1 tarball SHA1 to the registry metadata). Not verified: real-account wire behavior of gpt-6.1-sol, production deployment.