Loading page…
The server-controlled ChatPass meter tracks renewable usage windows apart from existing caps, but it remains unannounced and its eventual scope is unknown.
Listen to this story
OpenAI’s Codex desktop client has a dormant, server-gated panel for a proposed ChatPass allowance system, suggesting subscription usage could eventually extend across ChatPass apps rather than rely on ordinary ChatGPT or Codex quotas. Builds 26.818.61809 through 26.820.71523 include the UI, localized in 64 language bundles, but a Pro account tested August 27 received no allowance data.
The panel appeared in three newer builds and was absent from 26.818.41509, despite that build already containing the app runtime.
Account servers, not a client experiment flag, determine visibility by returning chatpass.windows usage windows.
Observed fields cover percentage used, duration, and reset time; no prices, transactions, balances, or payment methods appear.
OpenAI’s Codex desktop client contains an unreleased Subscription sharing panel for a subscription allowance shared with ChatPass applications. The feature is designed as a separate meter from standard ChatGPT and Codex limits, yet one tested Pro account had no active allowance.
The dormant panel appeared in Codex builds 26.818.61809, 26.820.60940, and 26.820.71523. It was absent from build 26.818.41509, which already contained the client’s app runtime. Internal text says the shared allowance is for ChatPass applications, and the feature is localized across 64 language bundles in version 26.820.71523.
Codex can consume an optional chatpass.windows object from OpenAI’s account-usage endpoint. Each window carries a percentage used, a duration, and a reset timestamp. The client recognizes five-hour, daily, weekly, and approximately monthly windows, and can sort multiple windows from shortest to longest.
The panel renders only when OpenAI’s account server returns ChatPass windows; the client has no dedicated experiment flag around it. An authenticated request from a Pro account on August 27 omitted the object. A demonstration of the panel used synthetic allowance data, so it did not show an active customer entitlement.
The observed implementation tracks allowance windows, but it does not resemble a developer-payment system. It contains no prices, currency fields, checkout sessions, payment methods, merchant records, transaction histories, or balances payable to developers. That leaves the feature’s observed role narrower: displaying shared subscription usage rather than settling payments with app makers.
Codex recognizes app-related identifiers, including plugin and connector IDs, but the current panel shows only aggregate allowance use, a window length, and a reset time. It does not visibly identify the app consuming an allowance or offer per-app usage, consent, or revocation controls. OpenAI has not announced ChatPass or defined whether it would apply to in-product apps, external apps, or both.
Loading discussion...
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.