Use a launch offer to test useful work you already have. Wait for published terms before buying a rumored plan. Claude has a confirmed cloud-session credit offer for existing subscribers and a separate limit-reset feature. OpenAI has completed another announced Codex/Work reset, while discussion of an “o” assistant and a $500 Pro Max plan remains ahead of official product terms.
This is the September 27, 2026 check. For the released models, read our Opus 5.5 review and GPT-6 Sol/Luna comparison. The offers below do not establish which model produces better work.
For the purchase decision, the September value shortlist compares Claude Pro with Opus, MiMo, DeepSeek, Luna and the current OpenCode Go allowance. Its weekly-clock explanation separates idle time from accumulated capacity. This page tracks grants and announcements; the cornerstone playbook provides the reusable spending method.
What you can use, and what is still a report
| Item | Evidence and scope | Practical decision |
|---|---|---|
| Claude cloud-session credit | ClaudeDevs announced $100 for existing Pro subscribers and $250 for existing Max subscribers | Check your account’s offer and supported session type before claiming |
| Claude limit reset | Official help documents an eligible, user-controlled refill of the displayed session or weekly limit | Read which limit and expiry your reset covers |
| Codex/Work incident reset | Tibo announced it September 26 UTC and later reported propagation complete | Check the account meter; this is not a future weekly promise |
| OpenAI DevDay | Official event: Tuesday, September 29, San Francisco | Watch the keynote for actual releases and terms |
| “o,” “Aeon,” and Pro Max | Dated reports and screenshots; product scope, model identity, prices and entitlements are unconfirmed | Keep them off your purchasing and capacity assumptions |
Sources and the boundaries behind each row follow below.
Claude’s cloud credit is for a particular kind of work
The September 23 ClaudeDevs announcement names existing subscribers: $100 on Pro and $250 on Max. Its offer instructions say to claim by October 7, through the linked claim page or /claim-credit in the CLI, and connect GitHub to start a session. The preceding post limits the grant to one per account and cloud sessions.
This is credit for Claude Code running in Anthropic’s cloud. It is not an AWS or Google Cloud coupon, cash, a subscription-fee discount, or general Claude API credit. Buying a new subscription today is not established eligibility by that announcement.
Anthropic clarified the charging order on September 24 UTC: qualifying cloud sessions use the promotional credit first, then fall back to normal plan usage. Separately, the cloud-session documentation says the VM has no separate compute charge and ordinary cloud sessions share account rate limits. Parallel sessions consume those limits proportionately.
That makes the offer useful for a bounded repository task you can review as a pull request: reproduce a bug, update a dependency, or implement a small feature with explicit acceptance checks. Someone who only uses Claude chat or local coding may get little value from this particular credit.
There are two deadlines to check: claiming the grant and spending it. A September 23 Reddit account report reproduces a claim deadline of October 8 at 08:59 GMT+2 and a spending expiry of November 5 at 08:59 GMT+1. Those correspond to October 7 at 23:59 PDT and November 4 at 23:59 PST. The same report excludes Projects and Routines. These are reported offer-screen details, not a universal eligibility guarantee; read the dates and exclusions in your own offer.
The promotional-credit terms allow offer-specific restrictions and authorize enabling Usage Credit when it is not already enabled. Check that setting and your spending controls after claiming. A promotional balance is a temporary opportunity to evaluate a workflow; keep paid overflow and recurring subscription cost visible.
A Claude reset refills a limit; it does not add cloud dollars
Anthropic’s limit-reset help says an eligible reset restores the limit shown in the offer: either the five-hour session allowance or the weekly allowance. The weekly schedule stays on its usual day and time. Redemption cannot be undone, does not refund billed extra usage, and does not change the credit balance.
Open Settings → Usage on the web or Claude Desktop and inspect the reset before confirming it. The help page says the button is not currently available in mobile, terminal, or IDE clients, although the replenished account allowance applies across those surfaces. Downgrading or cancelling before redemption removes the reset.
The Opus 5.5 launch has prompted reports of an October 22 expiry. That report concerns the saved reset, not the cloud-credit spending deadline. Treat it as an account report and use the expiry displayed on your reset. A saved reset and a cloud credit can appear together while funding different usage. Neither establishes a permanent increase in weekly capacity.
Codex: a banked grant and a separate incident reset
OpenAI’s September 22 launch announcement also relays Tibo’s banked-reset grant for Plus, Pro, and Business accounts. The official banked-reset help explains user application and expiry; check the remaining count and deadline in your account. It is separate from the later incident reset below.
Tibo Sottiaux’s September 26, 00:07 UTC post announced a reset for paid Codex and ChatGPT Work users following a disruption. At 18:17 UTC the same day, he said propagation was complete. That is the provider’s report; we have not verified every account meter.
The circulating “almost Tuesday” post was published on September 22 UTC. It should not be read as a September 29 promise. We have not established a fresh September 29 reset commitment in this review. Schedule work against the allowance you can see, and use a discretionary reset if it arrives.
Plan access also has a material update. OpenAI’s Pro FAQ, checked September 27, still pauses new Pro $200 subscriptions and upgrades. Existing renewals continue and Pro $100 remains available. However, eligible former Pro $200 customers can now return once within 30 days after access ends. The FAQ requires access on September 10 or access that ended in the preceding 30 days, with the one-time return unused. Sign in to the same account to check eligibility; returning starts a paid subscription.
Our Codex verification record carries this correction. Older claims that nobody can return during the pause are no longer complete.
DevDay, “o,” and a possible $500 plan
The official DevDay schedule confirms September 29 at 10:00 a.m. Pacific for the opening keynote. That is 17:00 UTC on September 29, or 01:00 Singapore time on September 30. The keynote will be livestreamed. The event schedule does not confirm a new subscription or a particular model release.
On September 24, TestingCatalog reported unreleased Pro Max references showing $500 per month and wording about faster Work and Codex. This is a report about development evidence. Higher allowances, a Cerebras connection, launch timing, and final terms remain unconfirmed. A price visible in a reported test interface is not a purchasable offer.
September 26 Reddit discussion of “o” describes an always-on assistant. A separate thread connects it to an alleged Astra variant called “Aeon.” These are useful leads for what to check after the keynote, not verified model specifications. We are not treating “o” as a released API model or assuming it is the older o-series reasoning family.
If a persistent assistant ships, the buying questions extend beyond its benchmark score: which plans include it, how unattended work spends allowance, when it asks for approval, what tools it can reach, and how you stop or review it. If Pro Max ships, compare the published capacity and speed against the work your current plan completes. Wait for those answers before attaching a value judgment to the rumored price.
Use the cost-saving playbook to compare accepted results, retries and review time. AIHackers has not redeemed these offers or run a paid comparison for this article; CAR is not-run. Recheck after DevDay and before each displayed offer deadline. Source archives remain archive-pending.