OpenAI’s Six-Month Pro Offer Is Still Open—but Its Value Is Unclear

OpenAI is still accepting applications from maintainers of active open-source projects. The live Codex for Open Source application remains available, identifies the review process as rolling and promises selected maintainers six months of ChatGPT Pro with Codex; it displays no closing date.

The important change since the offer began circulating is its less certain financial value. OpenAI’s current Pro-tier guidance lists monthly plans at $100 and $200, both with the same core capabilities but different usage allowances, while the maintainer application does not identify which tier successful applicants receive.

What the program provides

The subscription is the clearest part of the award: selected maintainers receive Pro access for half a year, and Codex is included. The intended work includes everyday coding, pull-request review, issue triage and other recurring maintenance tasks.

API credits and Codex Security require more careful reading. Selected maintainers may receive credits for coding, release workflows and maintenance automation, but no standard credit amount is published. Qualified repositories may also be considered for conditional Codex Security access when deeper security coverage is needed; that wording does not guarantee security access to every successful applicant.

This is therefore in-kind operational support, not a cash grant. It may reduce the cost of coding tools or help a project process maintenance work, but it does not pay a maintainer’s salary or reimburse time already spent.

Why the package no longer has one defensible retail value

The earlier four-figure valuation came from multiplying the former $200 monthly subscription price by the award period. That arithmetic is no longer sufficient because two retail tiers now carry the Pro name.

At current list prices, an equivalent subscription period would cost either $600 or $1,200. These are conditional calculations rather than values assigned to the award: the application names ChatGPT Pro without specifying the recipient’s tier, usage allowance or retail equivalent.

The distinction is material for maintainers planning demanding workloads. The lower tier carries five times the general usage allowance of Plus, while the higher tier carries twenty times that allowance. Access to the same named capabilities therefore does not establish how much parallel or sustained work an awarded account will support.

API credits could increase the package’s effective value, but there is no public figure to add to either subscription calculation. Any budget, sponsorship statement or project forecast that assumes a fixed total would be premature until the acceptance terms identify the tier, credit amount and applicable restrictions.

Who can apply

The program is aimed at primary or core maintainers of active public repositories. Selection considers meaningful usage, broad adoption, importance to the software ecosystem and evidence that maintenance is continuing.

The required application fields include a public GitHub username, a public repository URL and the applicant’s role. Applicants also receive up to 500 characters to explain why the repository qualifies, with stars, monthly downloads and ecosystem importance presented as possible evidence rather than mandatory thresholds.

That leaves room for infrastructure projects whose significance is not captured by GitHub stars alone. A focused application can establish the connection between the maintainer, the repository and the proposed use of Codex through a few verifiable points:

• State whether the applicant is a primary or core maintainer and ensure public project activity supports that role.
• Choose an adoption measure appropriate to the project, such as downloads, dependent projects or another visible usage signal.
• Identify a recurring maintenance burden, such as reviewing pull requests, triaging issues or managing releases.
• For API credits, describe a bounded project workflow rather than a general interest in experimenting with the API.
• For Codex Security, explain why the repository needs deeper security coverage and treat access as conditional.

Developers can apply for their own project or nominate another maintainer. Submission places the repository into a selection process; it is not an instant trial, automatic entitlement or guarantee of acceptance.

What remains undisclosed

The public materials provide no acceptance rate, recipient cap, response-time commitment or standard API-credit allocation. An independent OSS.Fund listing marked the program live and verified it on March 15, 2026, while recording that recipient totals and aggregate credit amounts were not publicly available.

That verification also supplies useful historical context: the offer was already operating in March and should not be treated as a new August launch. Its continuing relevance comes from the application remaining open and the later introduction of two differently priced Pro tiers, not from a newly announced giveaway.

The absence of published totals limits broader conclusions about the program’s scale. A live application establishes that submissions are being accepted, but it does not reveal how many maintainers have been selected, how quickly decisions are made or how much infrastructure support has been distributed.

What maintainers should take from the offer

For an active maintainer with a public repository and a defined maintenance workload, the concrete benefit remains substantial: an awarded Pro subscription includes Codex, with possible additional support for API-based automation and repository security. The application is short, and the published criteria allow projects to explain ecosystem importance even when conventional popularity metrics are modest.

The offer should nevertheless be evaluated on its confirmed terms rather than a headline dollar figure. Its retail equivalent depends on the unspecified Pro tier, while API credits and Codex Security have separate uncertainties. If selected, a maintainer should verify the awarded usage allowance, credit amount and redemption conditions before building a project plan around them.

Also read:

• VLMs Can Already Hunt for the “Interesting.” But They’re Still Bad at Walking Away from What They’ve Found
• Figma’s Design Agent Is Open Beta—Paid Access Still Has Boundaries
• OpenAI Merges ChatGPT and Codex into One App After GPT-5.6 Launch, Introduces New “Work” Mode