OpenAI is building "Subscription sharing" for AI apps

Finding

OpenAI’s desktop client contains a hidden account meter for **“Subscription sharing.”** Internal copy describes it as showing how much of a user’s subscription allowance is shared with **“ChatPass applications

How we verified

Methods: reverse engineering.

The Codex desktop client fetches account usage from: ```text GET /wham/usage OAI-App-Brand: chatgpt ``` It expects this optional structure: ```json { "chatpass": { "windows": [ { "used_percent": 0, "limit_window_seconds": 604800, "reset_at": 1788468559 } ] } } ``` When those windows exist, the app creates a separate **Subscription sharing** section and displays each as a renewable usage meter. The client: - Converts `used_percent` into “% left.” - Recognizes five-hour, daily and weekly windows. - Supports an arbitrary number of windows. - Sorts shorter windows before longer ones. - Displays reset times. - Keeps ChatPass separate from ordinary ChatGPT/Codex limits, credits and workspace spending controls. This is quota infrastructure, not merely marketing copy. ## Why the mini-app connection is plausible The same client already understands app-runtime identifiers including: - `connector_id` - `plugin_id` - `canonical_app_id` - `app_name` - `resource_uri` Those power the plugin/widget system we covered. OpenAI’s public architecture likewise lets plugins ship interactive UI associated with tools through a UI resource URI. [OpenAI’s plugin UI reference](https://developers.openai.com/plugins/reference#tool-descriptor-parameters)

Tested versions: OpenAI.Codex_26.820.9563.0_x64.

Reproduction

RuntimeWire independently reproduced the core finding.

File hashes

• ASAR SHA-256: `E353C580EF4939D36F4AE32A35C896D089205C1D06B9F711CF78FFA4A3578A8A`

Company response

RuntimeWire requested comment; the company had not responded by publication time.