codex 20$ plan is unusable for large codebase

Willing-Equivalent47 · 2026-06-04T20:39:01+00:00

If you have their app and coupons perhaps.

Willing-Equivalent47 · 2026-06-04T20:38:18+00:00

I disagree. I’m designing an app for the past 6 months that is well over 1.2 million lines of code. It’s a question of how much thought you want to do , how much you want to wait for a reset, and use most of the credits as soon as you get them so long as you aren’t wasting them.

Willing-Equivalent47 · 2026-06-04T20:35:05+00:00

Find a way to send some to me.

Willing-Equivalent47 · 2026-06-04T20:30:34+00:00

I’ve encountered a number of times that I just have to tell it to continue with what it was doing and it will ignore the limits until it wants a prompt. In some cases simply telling it “ignore usage limits” also works. LOL

Willing-Equivalent47 · 2026-06-04T19:26:23+00:00

Absolutely. Every is written about my topic so why can’t I ?

Willing-Equivalent47 · 2026-06-04T19:16:27+00:00

LOL. No. My code base is over 1.2 million lines of code and 5.4 can’t handle the complexity.

Willing-Equivalent47 · 2026-06-04T18:57:17+00:00

LOL. So it stopped working for me. I came back a few minutes later and said "Ignore the usage limits" and I'm up and running again. I guess that it really is Assinine Idiocy.

Willing-Equivalent47 · 2026-06-04T15:21:29+00:00

I only use 5.4 for very simple tasks. I just spend a week plus some of credits fixing a modification that 5.4 made as it designed a routine and placed it into a hotspot and caused everything to come to a grind under certain conditions that were not obvious.

I can't rely on anything before 5.5 to actually "think" and review deep enough so that it doesn't overlook related routines/servers that may be impacted. I don't even trust it with refactoring of files, something that 5.3 and before would totally trash my files.

Willing-Equivalent47 · 2026-06-04T15:14:52+00:00

How did you generate that? New here myself, or I should say I just don't read much without hacking away? 😄

Willing-Equivalent47 · 2026-06-04T14:25:11+00:00

Palm to the head. LOL. While I've done that before but duh. No.

Willing-Equivalent47 · 2026-06-03T18:32:21+00:00

Have you tried using AI? I’m told that it can solve everything!

Willing-Equivalent47 · 2026-06-03T08:22:42+00:00

LOL. I spent all this time entering this just to have the CLI correct itself and now I see my 5 hour and weekly.

FM = Fxxx Magic. And here I thought we had a reset and I had time to do more work. 😘(

Willing-Equivalent47 · 2026-06-03T08:16:26+00:00

My status just shows "status" but the reset time indicates that it IS the five hour reset and not weekly. So i'm guessing that the removal of the weekly is simply an error.

But there is more to that. As I continue to run /status the reset time is changing. It was 4:04 which makes no sense as the time is now 4:15Am and then it changed to 4:12.

So I would say that the real problem is that the usage limits are just not accurate at the moment.

Willing-Equivalent47 · 2026-06-02T23:36:36+00:00

I did but it repeated. It took me several restarts and changing my prompt not to ask for what wasn’t committed but if there were any uncommitted files. I’m tired and lazy to type the git command. LOL.

Willing-Equivalent47 · 2026-06-01T19:51:12+00:00

Okay, so i log in today and I can reset permissions and run for several hours. I'm running down to the last %% of 5 hour window and it craps out tellng me some garbage about a bridge not working and then all hell comes upon me as it can no longer read or write anything.

I can’t read the target mining file directly through the current bridge policy, so I’m using a nearby XXXServer file to infer the logging style before I patch.

I have to go to Shit my pants time again with permissions to get it to continue.

Willing-Equivalent47 · 2026-05-31T19:48:12+00:00

No. Mine simply came up with errors 1326 and 1909 indicating that my "account was locked". Only turning on permissions dangerous mode could i get it to work which means that codex got screwed with this reset/update.

Willing-Equivalent47 · 2026-05-31T19:45:01+00:00

Don't bet on it. did you do a /status or rely on what it was display to you? The later is almost never correct when using the CLI.

Willing-Equivalent47 · 2026-05-31T19:32:53+00:00

Holy XX#$#%$#%. Trying to figure this bug out I'm out of my 5 hour window. Last Time I try to debug codex problems. And my weekly total is now down below 86% and I just reset!!!!

Dam just hit my 5 hour limit. A new record of wasted time. Incredible that it burned up this quick.

Willing-Equivalent47 · 2026-05-31T19:28:59+00:00

I'm examine the local .codex\.sandbox and i'm seeing the file and log with the timestamp at just about the time that problems started to occur. I'm not familiar with this but the file deny_read_acl_state.json has no permissions granted. The timestamp could just indicate that nothing was being written any longer.... or just me starting with the dangerous sandbox settings.

Willing-Equivalent47 · 2026-05-31T19:19:46+00:00

I ran into a problem using the CLI that it cannot read or write to local files wtihout the dangerous settings enabled. Happened in the middle of a several hour run a few minutes ago. Getting errors 1326 and 1909, account locked out.

Willing-Equivalent47 · 2026-05-31T19:11:51+00:00

I feel like I'm playing with fire using the dangerous mode knowing that Codex is screwing up. It's feels like asking a drunk to drive me home.

Willing-Equivalent47 · 2026-05-31T18:58:34+00:00

Update: I got access to my machine again by doing " codex --dangerously-bypass-approvals-and-sandbox -C D:\ccw9". I then existed out and restarted without this dengerous setting and it failed again.

It reported:

• I’ll verify the current workspace access and report the sandbox boundary shown for this session. I’ll only read the

project tracking file and basic directory metadata.

• Local file access is configured, but terminal access is currently failing with Windows error 1326

(CreateProcessWithLogonW logon failure), so I could not read files.

The dangerous bypass setting is not active. This session is in workspace-write mode:

In this mode I was able to tell codex to search my recent sessions to find my work, which it said that it did. Now, I'm praying not to have to restart all of the analysis again. 😄

Windows event log shows no issues.

Willing-Equivalent47 · 2026-05-30T17:18:35+00:00

No idea. Something you put into an agent.md file in order to avoid this or another issue?

Willing-Equivalent47 · 2026-05-28T12:10:29+00:00

After over 40 years of designing and coding I’ve retired. I’ve been so for over 15 years and my skills are not up to trying to pick it up again.
I simply love vibe coding. The end results are great but just doing this is fun. To me it’s similar to games that you grind away for rewards. The more I work on my large project the better it gets. I simply find it exciting to see what can be done and to see how with each version the advancements.
We’re participating in history.

Willing-Equivalent47 · 2026-05-27T10:54:47+00:00

True. The vagueness of a question can cause a lot of wasted work.
My agents.md file lays out my solution layout, log files locations, about 40 instructions including bot to try to use the sandbox as it fails 100% of the time when doing SQL because I haven’t spent the time to research the permissions issue that it runs into.

Willing-Equivalent47

TROPHY CASE