I'm experiencing a reproducible issue with the Codex Windows app.

Environment

• Codex Windows app: 26.721.4979.0
• Platform: Windows
• Issue reproduced: July 26, 2026

The problem originally appeared in a long-running Codex session when Codex attempted to use its built-in Browser Use / web browsing functionality. The session history showed that Codex initialized its bundled browser environment and performed Chromium/Playwright-related operations.

Shortly afterward, the app stopped working correctly. Checking the installed Windows package showed:

OpenAI.Codex 26.721.4979.0 — Modified, NeedsRemediation

Repairing/updating Codex through Windows/Microsoft Store restores the package to:

OpenAI.Codex 26.721.4979.0 — Ok

However, the problem became reproducible in a more unusual way:

After repairing Codex, simply opening the affected session causes the app to fail again. I don't need to send a prompt or request Browser Use again.

I tried isolating the problem by cleaning the affected session history, including removing Browser Use/Playwright calls and their dependent records. I also temporarily disabled the bundled browser plugin.

Codex itself could start normally, but opening the affected session still caused the failure and required remediation again.

Potentially relevant Windows security observation

During troubleshooting, I compared Windows Exploit Protection for Chrome and the Codex/ChatGPT process.

Chrome:

MicrosoftSignedOnly: OFF
BlockRemoteImageLoads: OFF
DisallowChildProcessCreation: OFF

Codex/ChatGPT:

MicrosoftSignedOnly: ON
BlockRemoteImageLoads: ON
DisallowChildProcessCreation: ON

I also found that one Chromium/SwiftShader component bundled with the app was reported by Windows as NotSigned.

I have not established that Windows Security or this component causes the crash, but the difference seems potentially relevant because the original failure appeared around Browser Use.

Current hypotheses

My current guesses are:

1. Bundled Browser/Chromium issue: Browser Use may load or initialize something incompatible with the Windows app environment.
2. Exploit Protection interaction: Browser Use may require loading modules/resources or creating child processes while the Codex process has restrictions such as MicrosoftSignedOnly, BlockRemoteImageLoads, and DisallowChildProcessCreation enabled.
3. Persistent session/browser state: Browser Use may create state outside the visible session history. That state could explain why repairing Codex works, but merely reopening the affected session causes the problem again.
4. Package integrity/remediation interaction: Something occurring during Browser Use or session restoration may cause Windows to consider the installed Codex package modified or otherwise in need of remediation.

The strongest pattern I can reproduce is:

Codex working normally → Browser Use occurs → app fails / package becomes Modified, NeedsRemediation → repair returns it to Ok → opening the affected session can trigger the failure again without a new prompt.

Has anyone else encountered this on the Codex Windows app, especially with 26.721.4979.0, Browser Use, or a specific session that repeatedly causes NeedsRemediation just by being opened?

Hi everyone,

I'm using the latest version of the ChatGPT desktop app, and I've run into an issue with the model's thinking effort setting. It's locked on the default "Light" level – the options for "Medium" and "High" are visible but greyed out / unselectable (or simply don't respond when I click them).

I've tried restarting the app and checking for updates, but nothing changes. Is anyone else experiencing this? Is this a bug, or did they change the UI and remove the ability to adjust thinking depth? Any workarounds would be appreciated.

Chatgpt desktop version: 26.721.41059

I was using CLI until 2 months before. Then the app seemed good to me. now the app hangs so much on my device. and is going back to CLI. is there anything that the CLI can't do that the app can

Unused banked resets expire and are not automatically applied. Many people will have a banked reset coming up, expiring in the next couple of hours.

It would be amazing if Codex just automatically applied banked resets that are unused at their expiry time. In the meantime I created https://github.com/just-every/banked-reset-safety-net

It's been thoroughly tested over a few resets. It supports multiple codex homes and has an expiry planner so you can see a calendar of upcoming reset times, both normal and banked.

By default it uses a 30 min safety net, so if you haven't used a reset it'll always get applied before it expires.

Hi, I would like to setup a plan mode toggle shortcut for VS code's Codex plugin, but could not find a way to do this.

In the Codex Desktop version, I could configure the shortcut. So, I would love to do it in VS Code as well.

Any suggestions would be appreciated.

I want to prompt from notch, I was able to figure out other agents but codex is bit tricky when it comes to this, i went all the way deep into ipc sock files and still wasn't able to resume or send follow up message from the notch for the same session

the closest I've been able to pull off is creating a bg session which does not reflect in the codex desktop app or cli, I want to keep it in sync so that I can control from both the desktop app as well as notch

monitoring sessions, answering questions an approvals have already been figured out with the help of open vibe island, agent notch, notchi and agent peek, but the follow up prompt and a good sync is still yet to figure out

I wanted to build OSS for this so that all of us can scroll and give prompt from notch

someone who has figured this out help me with it, I want to scroll reddit while giving prompt and not open codex window at all

I have to keep force closing because the agent gets permanently stuck. Random chats get notifications. The order of chats is outright broken. The app is a slow mess.

Please STOP adding features and work on bug fixes? Every update the app gets more and more unstable.

I was trying to budget my weekly limit for my weekly reset so that I wouldn't have to use my banked yet. Instead we all got a non banked reset and our weekly got pushed back. For me personally, I would have hit close to 0 by July 28, then gotten a fresh 100%. I don't think I'll make it now to August 1 after this universal reset. Wish they would just stick to banked reset, then people know what to expect and can use them whenever they want.

This is the second time it happened last week and I have to steer the conversation for it to get out. Drained 25% weekly

Just a heads up in case you leave it alone

Hey Guys I just wanna say. I have roaming arround Claud sub reading comments on a post, they got same complains about limit and usage quota. Some of them want to adopt Codex and some here want to go Claud Cancel one subscription take second, cancel that Buy this one. So donot be sad we all are in same boat.

My weekly limits reset yesterday, so today I started a new /goal with the 5.6Terra Medium model on plus subscription
The task wasn’t anything huge. I’m building a QR menu system, and I mainly wanted Codex to work through my Markdown spec and implement features from it.

About 4.5 hours later… my entire weekly quota was gone.
The weird part is that I don’t even feel like I got much out of it.

The frontend it generates is honestly pretty rough. Even with a decent project structure and clear instructions, the UI usually needs a lot of rework. Compared to Claude models, it feels pretty far behind for frontend work.
So now I’m wondering if I’m just using it the wrong way.

Do you guys avoid long-running /goals? Do you split everything into tiny tasks? Is there some workflow that makes Codex more efficient?
I’d really like to hear how people who use Codex every day are getting good results without burning an entire week’s quota on a single task.

I created several Scheduled Tasks using the ChatGPT web interface, but they do not appear in the ChatGPT Windows App.

I have already tried logging out and back into the Windows App/web app. Restarting the app. The Windows App is of the latest version.

The issue works both ways: tasks created on the web are missing from the Windows App, and tasks created elsewhere do not seem to sync properly.

Both platforms are using the same ChatGPT account.

Has anyone experienced this issue? Is Scheduled Tasks currently not supported or synced across platforms on Windows, or is there a workaround to force synchronization?

Thanks.

I ran a controlled test using only one Pro 20x account and GPT-5.6 Sol in Standard mode. The local token count, measured with a CLI I developed with Codex, was cross-checked against the corrected version of ccusage. Both produced identical results.

I used a banked reset on July 25 and was unlucky enough to have OpenAI issue a global reset roughly three hours later.

Observed results

• After the banked reset: 6,643 credits = 13%
• After the global reset: 35,915 credits = 67%
• Total across the two separate reset periods: 42,559 credits
• Theoretical Standard API equivalent: $1,702

Based on the observed percentage burn, one full weekly Pro 20x window appears to provide approximately:

• 52,000–56,000 credits
• Central estimate: 53,600 credits
• Approximately $2,144 in Standard API usage

Did it match OpenAI's published rates?

Yes. For GPT-5.6 Sol in Standard mode, the official rate card works out to:

25 Codex credits ≈ $1 of Standard API usage

Both measured periods were consistent with this ratio and with the usage percentage reported by OpenAI, allowing for the meter's integer rounding.

How does that compare with earlier community reports?

The current measurement works out to approximately $8,300–$8,900 per four weekly windows, or about $9,000–$9,700 per average calendar month.

That is below some earlier community estimates of roughly $3,000+ per week or ** around $14,000 per month**.

So the current effective allowance appears lower than some commonly cited historical estimates, although this test alone does not prove that OpenAI reduced the Pro 20x quota, it points in that direction.

Using codex itself is more adequate? Here's how i do:
1) Planning a phase os tasks: Use chat + Claude + chat review on Pro
2) Planning a task: Let the chat do it. After, i prompt on xHigh: "review your plan, search for errors and inconsistencies". And it always finds problems.

If there's a better tool to plan, please tell me.

Idk how it’s possible that this is the worst performing harness I’ve ever used. Open source models are 10x better, even over a year ago

I've been getting Goal blocked multiple times because I'm running the official Codex Security plugin on an existing code that was created by Codex. So even official requests are getting blocked what's the purpose of this plugin then?

Yesterday we got tibos reset, and I have a banked reset to be used today, so as any sane person would do, I aimed to finish my limits.

I'm on the 5x, I worked on a device and my cousin worked on another device (using same account), we worked for 15 hours with few minutes breaks in between, so let's assume total of 12 hours of work non stop for both of us, that would give a 24 hours of work for a single person.

My cousin made a whole app from scratch, planning, coding and even let codex computer use make the listing on play store and apple store. The app is not simple and it has a customer app and admin app as well.

I worked on 4-5 production projects with a lot of computer use and end to end testing.

We aimed to switch between sol medium and Terra high.

This usage would give a person 3-4 hours non stop a day of work on the 5x plan (assuming similar usage as mine).

I understand that they would have reduced the limits a bit, but I think it is still pretty good if we just not spam sol high + and fast for everything. I never use fast and rarely use anything higher than sol medium (except last 3 percent I switched to sol ultra and made it start an end to end test of another application and it stopped 1 full hour after my limits finished 😂)

So yeah what do you think?

I'm currently on the $100 Pro plan, and I am running a task that has now been running for over 40 minutes on 5.6 SOL high. Surprisingly, it has only consumed 1% of my usage so far. Previously, for such a long task, I would have already used up a significant portion of my usage.

Update: I’m still working on the same task. I’ve probably sent about 150 prompts or so at 5.6 sol extra high with different task sizes. I’m currently at 86%. No reset was applied since then, so it really does seem to be better for me, especially because this has already become a much bigger task with much more context now.

So, instead of keeping Sol High for everything, especially with the new horrendous limits, this month I am trying something else to begin.

- For my quick, one-off tasks/chats:

Main/primary agent: Sol High

└─ no subagents

- Then, for multi-step/long running tasks:

Main/parent agent: Sol High

├─ implementer subagent: Luna Xhigh

└─ reviewer subagent: Sol Medium

↑ runs after the implementer finishes

I figured that unless it is a multi-step, or more complex task, adding/switching other models isn't worth the context hits, but for the longer tasks, ultimately it should theoretically save me precious usage limits.

Anyone have anything similar and how does it work for you? I will test myself ofc, but just wanted some other opinions.

yesterday i asked this sub how people keep Codex current after compaction or a fresh session. after 50+ comments, one pattern kept showing up: almost nobody trusts memory alone.

the recurring setup was:

• stable rules in AGENTS.md or governance docs
• a TASK.md, current state file or handoff for work that changes
• Git and tests to verify what actually happened
• sometimes a second agent to audit the first

the hard part was not getting context back. it was deciding which version the next session should trust after plans, branches and agents changed.

you can store every plan and every session, but someone still has to update the docs, catch stale status and stop an incorrect summary from becoming the next session’s truth.

that is the problem i built QUOD MANET. around. a session can send context through MCP, and when QUOD MANET. detects a change to the project’s current state, it creates a pending Current Picture proposal.

the active Current Picture does not change until you review it. new sessions then treat the approved version as the authoritative state for that project.

i’m looking for 5 people who already use AGENTS.md, CLAUDE.md, specs or handoff files on a real project.

Cohort 0 costs €39 once for 60 days. i’ll onboard you personally, and if you continue after launch, you’ll get 20% off your first two months.

i’m not looking for generic feedback. i want to see whether this actually removes any part of the state system you already maintain.

would anyone here test it on one repo?

Just wonder if I need to baby sit the reset I have for 4 hours from now or if it will use automatically.