openai / openai/codex

Codex for Open Source: ChatGPT Pro grant cannot be redeemed by existing subscribers

Open
#38,587 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

Summary

The ChatGPT Pro benefit granted through the Codex for Open Source program
appears to be delivered via a consumer promo flow that rejects existing
subscribers, making the benefit unredeemable for any accepted maintainer
who already pays for ChatGPT.

Steps to reproduce
  1. Be accepted into Codex for Open Source (acceptance email received
    2026-08-07, subject "You're in").
  2. Be an existing paid ChatGPT subscriber on the same account and email
    used in the application.
  3. Click "Activate 6 months of Pro" in the acceptance email.
Expected

The 6-month Pro benefit is applied to the account, replacing or stacking
on the existing subscription.

Actual

The activation page returns:

Thanks for being a ChatGPT subscriber. Current or recent subscribers
aren't eligible for this promotion.

The benefit cannot be redeemed.

Why this looks like a bug rather than intended behaviour

The Codex for OSS eligibility criteria require a valid ChatGPT account and
do not exclude existing subscribers. The error text is generic
new-subscriber promo copy, which suggests the program grant is being
routed through a standard promotional code path rather than a
program-specific one.

Why there is no user-side workaround
  • Cancelling to clear the check is not viable: "current or recent"
    implies a lookback window, and Program Terms section 4 states benefits
    may expire if not activated within the specified period. Cancelling
    risks losing both the subscription and the grant.
  • Using a second account is explicitly prohibited under Program Terms
    section 6.
Support status

Contacted support via help.openai.com. First-line support was unable to
act on it. The acceptance email is sent from a no-reply address, and the
program has no published contact route.

Timing

The acceptance email arrived 2026-08-07. Program Terms section 4 states
benefits may expire if not activated within a specified period, but no
deadline is stated in the email or on the program page. If a redemption
window is running, it has been open a week already with no way for me to
act on it.

Environment
Request

Apply the grant server-side to the account, or issue a redemption path
that is not gated on new-subscriber status. Happy to provide the account
email and acceptance email headers privately.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or entry point is identified; start by reviewing the Codex for Open Source activation flow and Program Terms sections 4 and 6 alongside the acceptance email. Done means an existing subscriber can redeem the six-month benefit through a supported path, either by server-side entitlement or an activation flow that accepts the account.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.