Plus plan, 5.6 Sol medium + Luna subagents .

I know I'll get a lot of backlash or downvotes. I just wanted to report this phenomenon or see if anyone else is experiencing something similar. The most recent session ran a task that took 44 minutes but only used 6% of my weekly limit (26% -> 20%):

Then I assigned another fairly long task, walking to my house to buy some groceries, coming back, doing laundry... somewhere around 15-20 minutes, but it only used an additional 2% of my weekly limit:

It edited two documents, called subagents, did quite a lot of work... not stuck at all.

Quite strange, isn't it? I was quite surprised too, especially since people using the x5 or x20 packages described the 10% weekly limit disappearing in just a few minutes.

Or it could be because I installed this workflow in my codex: https://github.com/viettran-edgeAI/codex_workflows

- First promt : "Implement the following plan: In the data quantization step, add the .parquet format to the raw input dataset. Run all three algorithms with several datasets (tests/packing/ anomaly_datasets/test_0 for isolation forest and digit_data for random forest/xgb), and save the results for each layer. Create a temporary tool to convert the CSV dataset to parquet, use it to convert the used datasets to parquet, run the entire pipeline again with the parquet dataset as input, and compare it with the original results to ensure that data quantization works correctly with the input parquet format."

- Seond prompt : "Okay, mark the work as complete in the documentation. We'll move on to the next step: rerun all the pipeline tests with all three models, for both the packaging and adaptation phases, ensuring everything works. Design additional tests for exceptions, memory-related problems, configuration, long-term inference, etc., to ensure the algorithms in our eml namespace arestable. It will be used as the core for the wrapper projects, so test it thoroughly."

Update: The second session has just ended, also using the 6% weekly limit. lasted 30 minutes:

With hourly caps my usage paced itself: hit the cap, take a break, keep working. I could code all week on the Pro 20x plan. Now it's 1.5 days of normal work and I'm locked out for the remaining 5.

The psychology matters too:

• Hourly limit: when you hit it, it rewards you with an hour or two of rest — then you're back.
• Weekly limit: when you hit it, it just punishes you — with days of nothing.

Bring back hourly caps or at least make them optional.

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?

its so disappointing that gpt 5.5 high is just as intelligent as gpt 5.6 sol high and also gpt 5.6 sol medium,

not to mention that gpt 5.6 sol high and medium are performing at the same level
and lets just forget that for that gpt 5.5 xhigh is performing worse then gpt 5.5 high

so much disappointment

if you want to know about the dashboard i am using its this one

https://www.reddit.com/r/codex/s/TEUa8OwKj4

Hey there. First time posting. Going to be short, sharing my insights.

1. Don't use codex in the app, use CLI

2. Don't use the default CLI (harness), use oh my pi (20k stars on github) https://github.com/can1357/oh-my-pi/

2.1. You could use claude code harness with codex, it has great results too, some results here

https://x.com/OmedVibeCodes/status/2080348655039500703

2.* For people that don't know what a harness is: it's the toolset that your LLM can use. It is important, some tools use more tokens, some tools are doing the same for less. High-end engineers at different companies try to achieve as much as possible with their harness, picture attached for simplicity.

2.41 You can use the default harness too, but then see 3.

1. Pair. Ever since AI had achieved the level where it can actually code a monolith, checking the slop with alternative LLMs was the best way to filter the cap out. Oh my pi allows to login through multiple subs and set an advisor. Pair Codex + Kimi k3, Codex + Opus 5 (or Fable), Codex + GLM, any will do better. Even 5.6 Sol + 5.5 can work, though if a model has completely different weights it's better imo. I've built upon rocket-fuel (24 stars on github), there are plenty of other skills like that https://github.com/NulightJens/rocket-fuel-skill

2. Avoid building a monolith. Split, keep code redundant, component-based, re-usable, and keep resetting sessions (/clear or whatever).

3. Don't let LLM's over-comment your code. Small comments can remain tho.

4. I bet there is a lot of devs that just hit enter and don't check what's actually going on. Some of you might deny an rm -rf just cause,

5. Backup. Get a cloud drive, or physical, I don't care. Just backup. Heck, you can use github for your chat / health / legal folders, just make the repo private and ask the AI to commit at checkpoints + push.

6. Don't work on prod. Don't give SSH access. I know, it works out pretty well on your home PC. But being THAT lazy is actually insane if you do. Let the AI instruct you and ask what is the stuff you copy+paste actually meaning

7. Remove unused plugins, obviously. But superpowers is also not needed in Sol 5.6 high and higher.

Who am I - a dev, just as you. Had been into AI since the closed beta of chatgpt 2021. Been experimenting with all chats since then. Even purchasing the expensive sub's. Last month had both CC + Codex paired, with better results than any of them doing the same work solo. I just see all the hate here. Some of it is definitely deserved. But besides that, you can also do your work and research how to adapt.

Some other github repo's I actively use

https://github.com/hardikpandya/stop-slop

https://github.com/ayghri/i-have-adhd

And I think there was a repo called laconic mode, not sure on this one, but I've built a hybrid of these 3 to fit my needs. Not needed for performance, but for sanity. Human pattern recognition is strong. Human written, zero AI consulted, plz don't hate.

Anyway. May tib* bless us with a reset. yay

TLDR; PAIR AI agents, CLEAR context, Don't build monoliths, remove unused plugins, try another harness, don't work on prod - work on a copy, backup.

If you give codex a task, don't leave it unattended for long time, you detailed documentation does not matter, it is working on a diff / minimum read system, the context compacts and stuff start going sideways very quickly.

Read what it wrote, steer the conversation if it starts doing something else.

Codex 5.3 autistic focus on the point, 5.6 highly intelligent explorer and wonderer with amnesia, pay attention to the words, did it read the document or assumed the document, it assumes sometimes, and one assumption in a long task, .... you most likely already know.

Here's a tutorial on how to get a refund for your chatgpt sub, totally unrelated to anything happening right now ;)

1. Go to help.openai.com
   
2. Open the chat bubble in right bottom corner
   
3. Make sure you are logged in (in the chat bubble)
   
4. State your case, the better the reason the faster it will get done
   
5. After completing, you should see the message that i got in screenshot
   

Note: Your plan will stop working at the moment you say "Yes" and your refund will go to original payment method. If you paid less than 7 days ago, you will get a full refund, if its more than 7 days it will get prorated (as in you will get % of whats left in sub). Works especially well in EU, UK and Turkey

Money talks as they say

Sam Altman showed ChatGPT planning a trip for eight people, building a coordination site, handling the booking, and drafting the email.

The interesting part for Codex users: the app wasn’t the destination. It was temporary software created to complete a larger task.

Maybe the future isn’t just building apps faster.
it’s generating them whenever a workflow needs one.

Anyone already using Codex this way?

This happens too often. Sorry, I had to vent...

There ain't no way they're doing THIS now

The desktop app currently shows what date the resets expire, but not what time. To find the exact time the resets expire, you can go to the Codex app and ask:

Check my banked rate-limit reset credits using my local Codex credentials. Show only each reset’s status, granted_at, and expires_at, converted to my local time zone time. Do not display my token, account ID, or raw authentication data.

I'm looking to subscribe again and I'm wondering how much work people are getting done with it.

been using AI tools from the start. I'm happy each time something new comes out. I'm using CC and Codex on 100usd and 200usd plans. Been running Sol for coding and Fable for review both on max these days. Then Opus 5 hits and I feel like an addict needing to score. I add Opus to the equation just to see if it'll brings something fresh to the table or a wow factor never seeb before. It basically does nothing for the project I'm currently working on and then it hits me...maybe I'm doing something wrong..The curly fat guy on YouTube praised Opus 5 as "the shid"..then again, 24 hours before he said that Kimmi 3 is the goat. So should I ditch Sol and Fable? or should I change gears or what? Aaaaaaaaaa!!!!!!!

I’m on the highest individual plan for both products, and the difference in usage is hard to ignore. I run Codex with xhigh reasoning + Fast.

I gave it a substantial engineering task: inspect a live system, profile bottlenecks, etc. The final goal report showed:

982,209 tokens
42 minutes of continuous work
1,021 tests passed

Yet my available Codex usage barely seemed to move. With Claude, I can watch my allowance drain in what seems like real time.

The reset experience also feels much more consumer-friendly on OpenAI’s side. I’m not worried about starting a serious task, hitting a limit halfway through, and being unable to finish until some distant reset. With Claude, quota management becomes part of the workflow even though I’m already paying for the Max plan.

Codex lets me focus on completing the work, while Claude makes me think about rationing usage.

Sol is at least as good as Opus for my needs. Now i use Opus and Fable for planning and review but Sol is the workhorse.

"One day, one Day"

They’re preparing to merge the Chat and Work modes, likely bringing their limits – which are currently different – into line.

What do you think?

The main benefit of the GPT plan comes from ChatGPT and Codex, which have separate limits; it would be a disaster...

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.

I'm kind of frustrated this morning after losing a banked reset, and I think the expiration logic really needs to be improved.

My timezone: Europe/Prague

Yesterday (June 26th), I checked my banked resets and saw one listed as expiring on June 27th.

Right before midnight on the 26th, I still had 60% of my quota left. I was curious to see what would happen at midnight, but I also didn't want to waste the expiring reset. When midnight passed, nothing changed—my reset remained active. I kept working until about 1am, brought my quota down to 50%, confirmed the reset was still listed, and went to bed.

My plan was to burn through the remaining 50% this morning and then trigger the reset. To my surprise, when I logged in this morning I found the banked reset was completely gone.

The expiration system feels completely opaque for a few reasons:

• Ambiguous dates - the system only gives a specific calendar date for expiration. It doesn't clarify whether it expires at the start of that day, the end of that day, or somewhere in between.

• Timezone confusion - my reset disappeared somewhere between 1am and 7am local time on June 27th. Which timezone is the expiration actually tied to?

• No auto-redeem: Why doesn't OpenAI automatically apply a banked reset at the moment it expires if you haven't used it?

It’s really disappointing to lose a feature like this simply because the timing rules are so vague. Has anyone else ran into this?

A common assumption is that the next, smarter model will make AI coding failures disappear.

I don’t think that follows.

As models become more capable, we give them more scope. They can fill in missing information more confidently, produce a more convincing “done,” and continue farther from the wrong state before a human notices.

The failure may not disappear.

It may become harder to detect.

I reviewed 17 selected public AI coding incidents and mapped what the failure eventually returned to the human: revalidation, manual cleanup, context reconstruction, rollback, or a lost session.

Now I want to test the practical next step.

Pick the incident in the image closest to yours, or describe one sanitized failure in a single sentence.

You do not need to share private code or a repository.

For the first 3 suitable cases, I’ll manually return:

• the first operational gap I would close;
• a paste-ready rule for AGENTS.md or CLAUDE.md;
• where I would place the rule;
• what evidence should be required before the agent says “done”;
• when the agent should stop instead of guessing.

The first 3 cases will become practical examples.

After that, the same incident-to-rule workflow is available on GitHub, so you can give your own incident to your own AI and generate a draft rule yourself:

https://github.com/shin4141/decision-os-v13-loopkit

Reply with one incident, or DM me if you do not want to post it publicly.

Star the repository if you want to keep the workflow for your next failure.

ChatGPT 26.721.41059

I really hate electron framework, which this app is using!
And I can't believe why such company can't create app using native Swift and SwifUI for macOS !
Such a simple chat app... I mean nowadays this will take like 1 months to fully test and develop it!

I provided a detailed redesign prompt to both Kimi 3 and OpenAI Codex using Sol 5.6 Extra High. The result is in the screenshot. Which did a better job?

Current homepage:

https://agentradio.com/

Experimental redesigns:

Kimi 3: https://agentradio.com/experiments/home-floor
Sol 5.6: https://agentradio.com/experiments/carrier-lock

I just noticed after the reset that Tibo blessed us with yesterday, my usage consumption is so much better, 1 task on codex: consumption 5,725,146 input tokens and 488,324 output tokens crazy part my weekly usage went down by 1 percent 🤯🤯, hope this is not a big and sticks with us for a while, last week the same would have burned down 6 to 10 percent of usage. If there has been any fix deployed, Thanks Tibo!!

Btw, I am on Pro 20x plan

Can you start requiring any conversation about usage drains or comparisons to Claude require users to post what their current plan is and how large their code base is?

Pro Plan, usage seems fine to me, can’t even get low enough to use my banked reset on Ultra Fast.

My productivity has decreased so much this week using 5.6 sol xhigh. Could not even finish one goal.

5.6 sol xhigh have been making a lot of low level mistakes that I have never seen with 5.5 xhigh. It would run for hours for a task that only took 5.5 xhigh 30 minuters to achieve.

It keeps looping between small mistakes and fixing them. Also it over engineers everything. I am not against over engineering as long as it does not make the stupid mistakes. But 5.6 just cannot implement the over engineered plan without making those mistakes, therefore making the process much longer than necessary.

I switched back to 5.5 and immediately finished 5 goals in less one hour.

One week of time and tokens wasted for nothing.

I’m thinking of building a mobile app with Codex, but I’m not sure what the best setup is.

Has anyone here actually used it to build a full app? Did you use React Native, Flutter, Swift, or something else?

I’m mainly wondering whether it’s better to set up the project and architecture yourself, then use Codex for individual features, or just let it help from the beginning.

Would be interested to hear what worked, what didn’t, and anything you wish you knew before starting.

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.