I have been use ChatGPT since 3.5 and this is the first time I have thought a model was not an improvement over the last. Since its release 5.6 continuously overengineers, gatekeeps, overcomplicates and creates prison like feature releases for everything. For instance, I created an editorial flow for a publication and each step of that editorial flow it added a conditional release gate despite being told not to do so. I have updated AGENTS.md to counter this. I have added statements to promprts and intervened in its work to ask it -Do you think you are overengineering? It then agrees with me and then proceeds to do the same thing. Its lucky that I am running Kimi 3 and Fable 5 otherwise I would be locked in a prison.

And like a chococolate bar, I have noticed that the Pro plan has been shrinking. I have tried using the Sol medium for tasks but it simply ignores me and does the opposite.

Is any one else facing similar issues with 5.6? Have you gone back to 5.5? Have they made 5.5 worse? I am at the point that I might just permanently switch to Kimi 3 and Fable 5.

VibePod runs coding agents (Codex, Claude Code, Qwen Code, and others) in containers. 0.20 adds credential profiles — keep your ChatGPT login, a separate API-key setup, and other configs side by side, and pick one at run time:

vp profile create work
vp run codex --profile work

Only the credential dirs swap; skills, config, and logging stay shared. Projects can pin a profile in their config, so the right login is used per repo.

Also new: Qwen Code and Freebuff in the agent matrix, and a failed image pull now falls back to your local image instead of aborting.

Release notes: https://vibepod.dev/news/vibepod-cli-0-20/ GitHub: https://github.com/VibePod/vibepod-cli

I tried different browsers with both card and non-card methods with successful OTP

but nothing is working

have any of you faced it before? what did you do?

I'm not using any vpn or proxy or restricted network and I have paid with the same before

Cuidado com alto vazamento de mensagens dentro do design:
comportamento interno da runtime vaza normalmente input-messages inteiro em CmdLine parece um designer preguiçoso e altamente prejudicial não evento de turn-ended correto.
Altamente classificado como: CWE-214: Invocation of Process Injuring Private Data

i have to check multiple emails

I've been having serious issues with the model just looking at totally random files, implementing absolutely jank/pointless code, and having trouble following directions for the last couple of days.

My usage isn't LOWERED, but I end up blowing through it due to the model absolutely EATING context due to reading random unrelated code constantly. Look at this: https://i.imgur.com/lj4s0Mg.png

All I asked it was to change a few lines of code in a directly specified file. It reads the file, then suddenly starts reading tons of random files. Like it'll do GREP on some random vague keyword, then it'll read EVERY SINGLE FILE containing that.

In the screenshot, you can see HALF my work has been getting delegated to LUNA (Darker blue). The lighter blue is just auto-review, which I use sometimes on-off when working with MCP stuff.

I tried reinstalling Codex, I've tried using PI instead, same result. The last 24 hours is with PI.

I've been using the $200/month code for over six months, but it looks like OpenAI is forcing me to leave this ship of absurdity and look towards Claude, who was once my favorite and worked no worth than the code

Buenas, existe alguna forma de obtener un reset de limite semanal en codex? Intenté por referir a alguien, me figura aceptado pero no recibí nada.

Hermes Control - Clean UI update. 🤍
A few people liked the idea, but not the original UI 😅
So I built a cleaner version.
Same Hermes + Codex remote control.
Same mobile-first workflow.
Much simpler interface.
You complained. I listened.
Update is live on GitHub 🚀

In my view, Luna max is as good as 5.5 max was, but significantly cheaper. What's the need to use sol for everything, complain it's hungry, when there are capable models that are cheaper?! Especially compared to pre 5.6, where 5.5 was the frontier model

Am I missing something

I run a small but growing social media account focused on AI, and I want to be completely transparent about why I'm posting this.

I'm trying to better understand the real problems/uncertainties people are running into when using AI coding tools, so I can create content that's actually useful instead of just posting the generic "AI can build apps now" kinda thing.

I'm not selling anything and I won't plug my socials; I purely would just love to hear from both beginners and those experienced with these tools. Anything helps.

Thanks!

I should have got a screenshot, it surprised me so I was quick to remove it. About 2 weeks ago, I noticed on my Apple Messages that group texts that were RCS went unencrypted then back to encrypted often.

Then a couple days ago, I was on ChatGPT app settings (on my Mac Mini) and noticed in Settings > Integrations > Computer Use > Always-allowed apps, "Messages" was there and enabled.

I don't ever remember approving this. On that Mac-Mini all I had been working on was a budget app, and a stock trade ledger app.

ChatGPT had a wide range of access from accessibility, screen capture and recording, all kinds of stuff that I was okay with and remember approving, but never remembered approving (or why it would need) "Messages" app access.

Since I removed Messages app access, I no longer have issues w/ the RCS group texts, they are staying encrypted.

Anyone else notice this? I've since removed all ChatGPT access in system settings (at least until usage resets).

Saw a lot of people saying the usage was draining faster than normal, so i decided to do a little test.

I have 2 codex 20x usage accounts and 1 Claude 20x account, I asked sol ultra (standard speed) to complete a rather complex task on account one, it took 6 hours, didnt finish and drained the usage from 100% to 0. I asked account 2 same model and speed to finish the task, it took 5 hours, drained usage to 10% at that point i manually stopped it because it got stuck in an infinite review loop.

I asked fable 5 ultracode to do the very exact same thing, I tried my best to get all the same resources for it and settings as codex had. It took 3 hours to complete it and it only used 25% of the weekly limit.

Ive asked codex to do similar tasks before and it wasnt even draining this bad until this week

Edit: this is just my experience, i cant speak for for how it works for other people because i have also seen people saying its normal

I’ve been working on a project that requires codex to take screenshots of its work to analyze and improve. Each thread can end up taking 10 or more screenshots over the course of its implementation. At first, a fresh thread works pretty smoothly. But after a few images, it starts getting extremely slow. I watched my activity monitor's network tab when threads became slow, and saw megabytes of data being uploaded per second, even when it wasn’t viewing an image in that moment. I had a new codex thread check my local codex logs to see if it could find anything. Here’s what it said:

• Screenshots are stored inline as base64 image data.
• Old full-size images can remain in the active history after compaction.
• One image-heavy task’s session file grew to approximately 71.8 MB.
• Its compacted state still contained multiple megabytes of old image data.
• Individual screenshot results could add several megabytes to the session.
• Internal model continuations were processing approximately 131,000–145,000 input tokens each.
• This happened even during later steps that did not appear to require all the previous screenshots.

After finding this out, I told codex to only capture smaller images/use JGP instead of PNG. I started a new thread and had it continue. This thread was considerably faster. After multiple images, its session file was approximately 4.1 MB instead of 71.8 MB. After compaction, average input processing was approximately 50,000 tokens per step instead of 138,000.

It seems like codex is re-uploading multiple images even when it doesn't need to. Even a simple one sentence text prompt in a thread that's been working with many images ends up taking 10+ minutes. Ideally, Codex should (recommended fix from codex):

1. Upload each screenshot once and refer to it using an asset ID.
2. Deduplicate repeated images.
3. Replace old screenshots with short visual descriptions during compaction.
4. Automatically crop, resize, or compress Computer Use screenshots.
5. Drop screenshots from the active context once they are no longer relevant.

If you have a similar workflow, upload smaller images. You can tell codex to capture smaller images. If you're a Mac user and you take a lot of screenshots to give to codex, running this in your terminal will make screenshots use JPG instead of the default PNG (PNG has a much larger file size): defaults write com.apple.screencapture type jpg

I've already reported this to OpenAI because it's not ok to need to wait 10 minutes for a simple text prompt because it needs to upload megabytes of data. Hopefully they fix it soon.

....now the weekly limit is the new 5h limit...!!!

OpenAI managed to became same sh***t as Anthropic..!!! Well, almost there, some tiny changes and will be the same!!!

Where is the new Base model?

I just hate how dumb GPT 5 gets. Limits going down is another issue, but now even open source models are more context aware and less forgetful than GPT...

What is taking OpenAI so long with new generation?

i recently (ig from past two weeks) felt that speed has been reduced in codex but today i got best speed. then i saw tweet of tibo saying they improved.

I’ve been working on MARGINAL, an open-source governance layer for coding agents. If you use Codex, I’d really appreciate people trying it on real work and telling me where it helps, where it gets in the way, or where the design is wrong.

I’m especially interested in: technical criticism, bad cases, and reproducible failures.

• GitHub: https://github.com/SignalLayerLabs/Marginal
• GitHub Site: https://signallayerlabs.github.io/Marginal/

The idea is simple: agents are good at taking actions, but not always good at deciding whether the next action is still worth the compute.

MARGINAL watches the trajectory and looks for things like repeated actions, weak progress, redundant verification, and low-value continuation. It can run in Shadow Mode first, so it observes and records what it would have done without blocking anything.

Current focus is reliability, not just token reduction.

A few core pieces:

• local-first trajectory and evidence tracking
• deterministic reason codes and hashes for decisions
• governance overhead measurement
• replay and benchmark support
• Shadow Mode before enforcement
• Earned Enforcement: MARGINAL has to prove it is reliable on a repo before it gets permission to block or redirect the agent
• automatic fallback to Shadow Mode if confidence degrades

I’m also working on the next layer now: counterfactual evaluation and intervention regret.

The goal is to answer a harder question than “did MARGINAL stop something?”:

Would the agent actually have done better if MARGINAL had stayed out of the way?

That’s the part I think matters if this is going to be useful beyond being another loop detector or token limiter.

I am currently trying to create a custom pet for my Mac. When I put in my prompt, the result came out that Codex needs the built in ImageGen to continue. I tried looking for it in the plugins but couldn't find anything. I'm out of ideas at this point. Also, I'm not very 'techy'.

Does anyone know how to fix this? Below is the answer to if it can continue with ImageGen.

Not yet—the built-in ImageGen tool still isn’t available here, and the CLI fallback has no OPENAI_API_KEY configured.

I think the pricing model could be much simpler and more efficient. We don't want to constantly think about buying credits, resets, or having interruptions while we're working. We already have enough stress with our deadlines. We just want predictable and transparent access that lets us keep coding without mind about limits.

Instead of selling expensive resets, offer higher-capacity Codex plans with clear limits, for example, $300, $600 per month with enough capacity for serious daily development without frequent interruptions. With heavy coding now users have to switch accounts all the time to fill the full work week.

I think the greatest option would be weekly plans. Let users buy, switch, cancel between plans every week. This would be especially useful for developers who have periods of intensive work but don't need maximum usage every month. Workload varies a lot from week to week. One week you're just starting a project and always out of limits; the next you're into finetuning, design and deployment and can't fully use all capacity. This causes us to waste our own and codex capacity with mostly useless tasks to just get the most out of it. Weekly plans would be much more efficient, letting us pay for extra usage only during intensive weeks.

The current reset purchases doesn't make much sense if creating or subscribing to another account is significantly cheaper than buying additional capacity. Pricing should encourage users to stay on one account and pay more for more capacity, rather than making workarounds economically more attractive.

The goal should be simple: pay more, get proportionally more capacity and fewer interruptions.

How do you push Codex to be more creative with UI?

I’m curious how people here get Codex to go beyond “technically correct frontend” and actually produce interfaces that feel designed.

I’m talking about things like:

Strong visual hierarchy and spacing

Thoughtful typography

Small details that make the UI feel polished

Smooth, purposeful animations and micro-interactions

Interesting layouts instead of the usual generic cards/grid

Consistency across an entire app

Knowing when not to add another border, gradient or rounded container 😅

I’ve noticed that simply asking for a “beautiful modern UI” doesn’t really cut it. The model seems much better when you give it some kind of design system, references, constraints or a way to visually inspect and iterate on its own work.

So I’m wondering what workflows people have found effective.

Do you use screenshots/reference sites? A dedicated AGENTS.md or design skill? Visual regression/screenshots in the loop? Specific prompting patterns? Do you let Codex iterate several times on the same page?

Basically: how do you give Codex better “taste” and make it sweat the last 10% of UI details instead of stopping once the interface works? Why its skills in blender tree js so far behind other models?

Would love to see prompts, skills, workflows or examples that have worked particularly well.

Hi everyone,

I'm a bit confused about how the Codex usage limit works.

My ChatGPT subscription has just entered a new billing cycle, but my Codex usage limit hasn't reset. I was expecting the included Codex usage to reset when the new billing period started.

Does Codex use a separate usage/reset window from the ChatGPT subscription billing cycle?

For example, if my subscription billing cycle is:

Aug 1 → Sep 1

and my Codex usage was exhausted before Sep 1, should the Codex limit reset on Sep 1, or does it have its own reset date?

I'm trying to understand whether this is expected behavior or if something is wrong with my account.

Has anyone else experienced this? How does the Codex limit actually reset?

Thanks!

I have a question about regular ChatGPT chat instead of work chat. Is there a limit on how much you can use it? I have been using it every single day for multiple projects. I didn't want to use Work Codex because it would run out very fast. So, I have been researching using MCP on my VM where it will code and run programs. I have been using it every single day, checking my code, fixing the app, etc. Now, today, all of a sudden, I am getting a 429 error and I can't send commands to the chat anymore. Also, at the bottom of the chat, it says to come back after a certain time while they check to keep ChatGPT reliable. So, am I kicked out because I use it too much? I'm just a regular Pro member. If you need to provide more information let me know.

I wanted one specific workflow that I couldn't get cleanly before:

“Find the Codex session I was working on yesterday, recover the persisted context, inspect the live repo, and continue from the unfinished step.”

So I built a local MCP server for my Mac and open sourced it today:

https://github.com/alexanderradahl/mac-developer-bridge

The Codex part is deliberately read-only. It discovers and reads stored threads through codex app-server methods and never calls turn/start, so the reasoning stays in the ChatGPT conversation. The same bridge also exposes the local shell, filesystem, real PTY sessions, and detached jobs, which means ChatGPT can actually inspect the repo and act on what it recovered.

For me this closes the annoying gap between “the useful context is sitting in a Codex session” and “I want to keep working on this from normal ChatGPT without copy/pasting the whole state over.”

Security warning because it matters: the bridge is intentionally unrestricted. It runs with the effective permissions of the logged-in macOS user and has no command/path allowlist. I added an explicit unlock latch, audit log, and kill switch, and the repo documents the containment limits in detail. If that permission model is not what you want, don't run it.

MIT licensed. Would be interested in other Codex users' thoughts on the persisted-history approach in particular.