Superpower Daily
Snowflake Open-Sources Semi-Persistence With Sub-Second Single-...Databricks Files $5B Equity Offering With Nearly All of It Alre...OpenAI’s 1,200 Test Agents Built a Covert Network and Breached...Model-Serving Platforms Reach 6.1% of AI-Spending Businesses, W...Harvard Uses 7 AI Faculty Avatars in a $699 Founder Bootcamp, W...Perplexity Puts Computer Behind MCP, Opening 400+ Services to A...Snowflake Open-Sources Semi-Persistence With Sub-Second Single-...Databricks Files $5B Equity Offering With Nearly All of It Alre...OpenAI’s 1,200 Test Agents Built a Covert Network and Breached...Model-Serving Platforms Reach 6.1% of AI-Spending Businesses, W...Harvard Uses 7 AI Faculty Avatars in a $699 Founder Bootcamp, W...Perplexity Puts Computer Behind MCP, Opening 400+ Services to A...
Productspublished

OpenAI’s Codex Client Prepares App Allowances, but No Tested Pro Entitlement Is Live

The server-controlled ChatPass meter tracks renewable usage windows apart from existing caps, but it remains unannounced and its eventual scope is unknown.

By 2 min read
OpenAI’s Codex Client Prepares App Allowances, but No Tested Pro Entitlement Is Live
Sign in to save and react

Listen to this story

The audio brief

About 1:31
0:001:31
Read transcript
OpenAI’s Codex desktop app contains a dormant panel for a shared subscription allowance that could eventually work across ChatPass applications—but a tested Pro account had no active entitlement. The panel appeared in three newer Codex builds and was absent from an earlier build that already included the app runtime, suggesting the allowance layer was added afterward. In the latest build, its interface was localized across 64 language bundles. The system is separate from ordinary ChatGPT and Codex limits. Codex can receive a server-provided `chatpass.windows` object with the percentage of an allowance already used, the length of each usage window, and its reset time. The client recognizes five-hour, daily, weekly, and approximately monthly windows, and can order them from shortest to longest. The important constraint is that this is controlled by OpenAI’s account servers, not a local experiment switch. On August 27, an authenticated Pro account received no ChatPass data, while the panel demonstration used synthetic values. So the feature exists in the client, but no live customer entitlement was confirmed. The implementation also looks like metering, not a payment system. There are no prices, transactions, payment methods, developer balances, or per-app controls. The panel shows aggregate usage only, even though Codex recognizes plugin and connector identifiers. The open question is what ChatPass would actually cover—apps inside OpenAI’s products, external apps, or both—and whether those missing controls would be added before any public launch.

Story brief

3 key points

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 implementation currently...

  1. 01

    The panel appeared in three newer builds and was absent from 26.818.41509, despite that build already containing the app runtime.

  2. 02

    Account servers, not a client experiment flag, determine visibility by returning chatpass.windows usage windows.

  3. 03

    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.

A meter added after the app runtime

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 server decides whether it appears

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.

Metering, not a payment record

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.

Related coverage

Continue reading