Codex updates paid-plan limits with a weekend reset

• Codex usage caps became the story this week: ClaudeDevs reset Claude Code's 5-hour and weekly limits on Thursday, then steipete's repost of Thomas Sottiaux said Codex limits were reset across paid plans on Friday.
• The paid-plan math is clearly visible in bas_fijneman's screenshot, which shows a weekly meter on a $100 Codex plan already down to 84 percent.
• Early hands-on feedback in awilkinson's Mac app review praised Codex for making 10 to 15 tabs easier to manage than terminal-heavy setups, while danshipper's reply said the app can control its integrated browser.
• Repo review is becoming a real Codex use case: steipete's clawpatch post showed a six-finding audit on a Swift repo, and steipete's repost of aleks_todo claimed a first pass found 27 issues.

OpenAI also pushed Codex onto phones via steipete's repost of OpenAI, with setup screens in LLMJunky's screenshot and petergyang's setup screenshot showing remote approval, computer-use access, and a Chrome extension hook. The odd little tell in this batch is that the most useful evidence is not a benchmark chart, it's a pile of workflow screenshots: repo audits, limit meters, and mobile review flow.

The reset posts landed a day apart, which made the contrast hard to miss. ClaudeDevs announced a reset of Claude Code's 5-hour and weekly buckets on May 15, and steipete's repost of Thomas Sottiaux said Codex limits had been reset across paid plans on May 16.

The pressure behind that reset shows up in bas_fijneman's screenshot, where a weekly Codex meter on the $100 plan was already heavily consumed. Several commentary posts in the evidence pool frame subscription access as the unlock, not just model quality, including steipete's repost of danmatern saying use through the subscription changed their main-agent choice.

The strongest product feedback came from awilkinson's Mac app review, which compared Codex directly against Claude Code on macOS and argued the visual tab model made parallel work easier to manage.

That same post surfaced five concrete friction points:

• AskQuestionTool is missing in work mode, so requests for input fall back to long text questions.
• Activity updates make the app feel slower than it may actually be.
• Human-style names for sub-agents are distracting.
• Settings and environment sync across multiple Macs is still awkward.
• Browser control was unclear enough that awilkinson thought it might be missing.

On that last point, danshipper's reply said Codex can control the integrated browser. That matches the remote-control setup shown later in petergyang's screenshot, which includes toggles for computer use and a Chrome extension.

A more interesting signal than the limit drama is what people are actually using the agent for. steipete's clawpatch post pointed to clawpatch.ai and included a repo review that separated one runtime bug from five lower-priority test and maintenance issues.

The findings list in that screenshot breaks down cleanly:

• A likely ffmpeg pipe deadlock in AttachmentResolver.swift
• A missing --chat test case
• Temp SQLite fixture cleanup missing on Linux tests
• Missing order assertions in helper-resolution tests
• A weak attachment staging test
• No smoke test for the actual @main executable

steipete's repost of aleks_todo pushed the same pattern further, claiming a first pass on another repo found 27 issues. That is a much louder pitch than "AI pair programmer." It is closer to automated code audit, with the output delivered as a review report instead of a chat transcript.

OpenAI's mobile push turned Codex into a review-and-steer surface away from the desk. According to steipete's repost of OpenAI, the mobile preview lets users start new work, review outputs, steer execution, and stay on top of long-running jobs from the ChatGPT app.

The setup evidence adds a few concrete details that the announcement post only implies:

• LLMJunky's screenshot shows QR-based pairing between desktop Codex and the phone.
• petergyang's screenshot shows optional settings to keep the Mac awake, enable computer use, and install a Chrome extension for web navigation.
• minchoi's video shows the phone UI handling review and approval flows, plus side-by-side diffs.
• LLMJunky's repost of Emanuele Dpt points to Remodex as a local-first, end-to-end encrypted way to reach Codex from a phone.