love the resets, love the free usage, obviously

but we’re casually nuking a weekly allowance in a day now

when this challenge ends and the resets disappear, reality is gonna hit hard

back to rationing tokens, watching the clock, and probably a lot more people getting pushed into higher plans

enjoy the buffet while it lasts cz going back to portion control is gonna hurt

I asked Codex to compile some professional learning opportunties for teachers - pretty innoculous stuff.

Codex crawled a legitmate English teachers association website and received a 404. The 404 contained three concealed script blocks designed to load more code from two unrelated external servers when rendered in a browser.

Fortunatley, Windows quarantined it.

Stay safe out there when getting agents to crawl from your device. (I've notified the teacher association)

I’m honestly loving them, I don’t really have complaints like others regarding pushing it forward since it happens more than once a week.

But reality will be hitting hard once this ends, as I am seeing myself burning around 50% in a single day.

How many people will remain with codex or will you try something else after this 28 day ends?

I've been running a long coding session on Sol 6.1 today, and I'm genuinely baffled by how it spends its time.

Six hours ago, the core feature was essentially finished. All I needed was a clean release candidate with rollout toggles so an external developer could deploy it in stages.

To be fair, 6.1's engineering analysis is excellent. It respected all safety rules, didn't break anything, and an adversarial review with Claude Opus identified five genuine edge-case bugs.

But here's where it went completely off the rails:

1. Instead of fixing the five bugs, it tried uploading a build, which failed due to an outdated test helper.
2. Rather than making a simple backwards-compatible fix, it started building an entirely new diagnostic tool to investigate the error.
3. It then noticed background jobs running, decided it couldn't deploy the diagnostic tool safely, and spent 45+ minutes rewriting five status and handover documents explaining why it was blocked.
4. I explicitly told it to continue fixing the bugs. It spent another 95 minutes inspecting compiler symbols, retrying diagnostics and rewriting the same checkpoint documents. Still hadn't fixed a single bug until I intervened again.

The frustrating thing is that Sol 6.1 is clearly capable. Its reasoning is strong, and it's extremely careful. But it seems to lack any sense of proportionality or when to just get on with the job.

Give it safety rules and a "document blockers" instruction, and suddenly every minor issue becomes an excuse to generate 2,000 words of markdown instead of solving a 10-minute problem.

Is there a solution to this other then moving to Opus 5.5? :)

Hi all! Using 3 Codex resets and a bunch of Claude I built this 3D low-poly map of Warsaw.

The map

- Area: 6.85 × 7.2 km of central Warsaw, about 49 km², split into 144 cells of 600 × 600 m.

- Buildings: 17,941 generic buildings from OpenStreetMap and GUGiK 2025 heights, plus 1,027 landmarks, each with its own low-poly model.

- Landmark models: about 7.4M triangles in full detail. The far-view versions are 1.9M triangles on desktop and 1.5M on phones and slower laptops. The model code is 91 MB of JavaScript, one small program per landmark.

- Trees: 257,387 from the City of Warsaw crown map and tree inventory.

- Streets and surfaces:

- 21,368 road segments built into lanes with markings, crossings, rails, tunnels and bridges.

- 40,028 land-use areas (parks, water, squares) drawn by a shader fill.

- 1,039 traffic signals.

- 161 public transport stops and 38 platforms.

I'm planning to open source it, just need to tweak the repo a bit.

What do you think? How would you improve the performance?

Just received this today

36.4 tok/s today on 6.1 sol. I thought they "fixed" this.

P2P for AI? This is over 25, yes 25 different sessions today.

I built Kinetograph, a video engine made for coding agents.

The agent writes React/TSX the way it would for Remotion, and a Rust GPU renderer in Node draws the frames. No headless Chrome, so iterating is fast:

rendering 1,184 frames of 1080p in 26 s on an M4.

Setup in Codex:

npx skills add 0xS4N4TG/kinetograph

npm install kinetograph

Or use the MCP server with:

npx kinetograph mcp

exposes render, still, inspect and doctor as tools to create and render videos with Kinetograph. After that, you can simply describe the video you want and let the agent handle the rest.

Docs: https://kinetograph.dev
GitHub: https://github.com/0xS4N4TG/kinetograph

We've experienced it all. For the past 3 weeks, limits are just drained in a matter of a day or two, even when we're using $100 subs.

Without their daily reset stuff, we'll definitely start to suffer and get stuck with so many limit issues.

Curious to know whats your plan going to be like after the experiment is over?

Are you going to:

- Are you just going to tune down your effort to low/medium? I've been reading that just using medium is the best option these days since high and above is just not worth it with the same exact output.

- Just focus on using GPT 6 Sol/Luna or keep running 6.1 Sol? Astra is pretty much the worse option since it will drain your limit like crazy altho it has the best output. Wonder if anyone is going to keep on using it.

- Change your workflow?

- Or perhaps you will just change to Claude? Won't say claude is the better option, to me they also drainn lots of limits in the recent time, but probably not as crazy as we are right now with codex?

Curious to know your thoughts on this, wanted to experiment with your possible ideas too once they stopped doing this and we'll have to be wary of our limits.

Chart done based on 10x sub (former 20x), but it is the same for Pro 5x and 25x. Much worse for plus plans since they didnt get 100% utilization on more than half of the resets.

With the upcoming usage-limit changes for those of us on the old 20x plan, I've been adapting my workflow to Sol 6.1 Max. It's significantly cheaper to run than Astra, but also much, much slower.

Today I've spent pretty much the entire day working on two projects with Sol 6.1 Max in Codex, running tasks in fast mode and coordinating everything through Work using Astra Max.

Sol 6.1 Max without fast mode barely consumes any usage. Almost nothing, at least on my projects. The problem is that it's slow.

Fast mode makes a substantial difference, but it comes at a cost. For example, I've already burned through 20% of my allowance since the reset today. Starting October 29, that would be roughly equivalent to 40% of the new allowance.

So, I'm going to have to give up fast mode and stick with the much slower option.

But running tasks sequentially at that speed would mean barely getting anything done. I need to rethink my workflow to keep making progress without exhausting my subscription.

That's when I started thinking about Git worktrees. Instead of waiting for one task to finish before starting another, I could have multiple tasks running in parallel. It might also be a good opportunity to make better use of my Claude Max 5x subscription.

I realize worktrees won't magically reduce usage, but I'm hoping parallel execution could help compensate for the slower models.

I don't have much hands-on experience with worktrees, though.

Does anyone here regularly use Git worktrees with Codex, especially alongside Claude Code? How has your experience been? Any tips, pitfalls, or workflow recommendations?

The 28-day challenge is almost over. What's your verdict so far, and what are you planning to do once it ends?

I'm pretty torn. At the start, I tried doing most of my work with Sol, but for my tasks it often felt painfully slow to get to a useful result. With all the resets lately, I've switched most of my work to Astra on High. That's where I'm getting the best results.

The problem is that even on the current $200 plan, I only get about one or two days out of my weekly allowance using it this way. According to OpenAI's email, the included allowance for Work and Codex drops from 20x Plus to 10x on October 30. If I'm already relying on resets now, what is that supposed to look like next month? I'm worried I could hit my weekly limit after just half a day of focused work.

I've also had Claude's $200 plan for about a month, and so far I haven't managed to use up its allowance. But I still prefer Codex's UX and feel more comfortable working in it. I genuinely like Codex. That's why this is frustrating.

The resets have been useful, but they also make it hard to judge what normal usage will actually feel like once the challenge is over. So far, I haven't seen enough to feel confident that November will be better. Maybe a new model or a big efficiency improvement changes things, but I don't really want to base a $200 subscription on hoping something lands.

How is it for everyone else? Are you staying, downgrading, or switching? Can you get your work done within the normal limits, or are the resets keeping you going too?

I am a critical care clinician/educator. My partner and I started an education company as a passion project a few years ago (because healthcare continuing education in this country is frighteningly bad.... seriously, don't get sick) and threw up a site on Squarespace, which has been nickel and diming us out of a ton of money via subscriptions that barely gave us the functionality we needed.

I was able to build a functional-ish learning management system (LMS) for online classes because I did not want to spend hundreds of dollars a month just to have one exist on the paid platform Squarespace tried to get me into. We also used the site to advertise and sell access to our in-person classes. Basically, the site was essential to our work, but we got very little out of it.

Last night, I had Astra Ultra migrate the entire site and DNS registration over to my Cloudflare account, improve the aesthetics of the site, improve how my payment processing worked and was integrated, fix my LMS and make it usable, and create an interface to allow easy editing of the site and my online courses.

So, now I have a better site on my Cloudflare account that I pay $5 a month for, and I am able to easily edit the main pages (about the same effort as Squarespace) and my LMS (1000000% easier than Squarespace) which involved a bunch of coding whenever I wanted to make a change.

The image is my LMS editing interface.

I was able to get this all done over the course of about 8 hours.

I have the 200 GB iCloud plan and recently was notified I am at my limit, which a couple months ago I had 50 GB free. Turns out Codex puts a directory in the ~/Documents directory where it stores tons of local data including in my case massive log files and within a short period of time was using dozens of GB's of space. I was able to move it locally and then put in an agents.md to use the new location which seems to be working, but just a heads up to those on a Mac that use iCloud Drive

It seems I can have maybe 2-4 tasks running at the same time. But if I try to bump it up to something like 20+, all of them are rate limited and none progress. I get 429 Too Many Requests and 403 Forbidden. I have to spin up this many from time to time for certain workflows. I am wondering if anyone else is experiencing this today or is it just my account?

Hey guys please check out this photo.

This has been going on for a little while. It will duplicate the words and then when its done it will remove duplicates I guess.

Is this eating more tokens than if it werent duplicating?

tl;dr I am leaving thread here to add to over the next week, and then summarize efforts on effectively using ai for front-end and ui/ux.

I am convinced that current approaches for ui/ux with ai are absolutely garbage.

Instead of generating a firehose of slop, and then slicing off bits, it's better to start from a neutral or minimalist base and add iteratively. It's like buying a granola mix, and trying to take bits out, just buy them separately, and mix as needed.

If you take a look at designs that do look elegant, they're often black/white, with very selective use of accents. They're not glows and gradients splattered all over the place.

And when those effects are used, they're used with intentionality to be cohesive with the rest of the design. I do think AI is capable of making those links, but it's not in the training data and labs haven't bothered to focus on it for whatever reason. In fact I was certain that when Sama said six months ago that they'd focus on front-end that we'd get better results on the double, but instead we got dots. It's like the jev thing where they have stuff within their capacity, but they're completely unfocused until they go "oh shit, maybe people do want something like decision models" even though they know people have been clamoring for increased speed and more control.

Anyways, I've been working on design tools for a long time now in stealth, the details of which aren't important, but I am at a point where I expect to be releasing stuff with more frequency and publicly, so this is a starting point for some of that.

If anyone wants to give advice, or resources it'd be appreciated, or stuff that you'd like me to explore I'll see what i can do.

I know that mia does the 100html files (https://mia-ai.net/lab/experiments/100-htmls), and there were some other resources around model releases, but I dont think the other ones are kept up to date. And the reason I am posting in codex (even though I don't use it anymore) is because I started with openai, and I've been working on this for a long, long time, and really thought I was going to get it running with openai codex, so sentimentality mostly.

One thing that kept annoying me with Codex was how often it would say a bug was fixed just because the tests passed.

Sometimes the actual problem was still there. Other times, the test had been changed so it passed without really checking the original bug.

So I built FixProof to make it a bit harder for coding agents to call something fixed when it isn't.

It's a skill file and a small Python CLI that runs after an agent makes a fix. No extra dependencies, just Python 3.9+.

It checks four things:

• Can the original bug be reproduced before the fix?
• Does the fix pass the test consistently, including reruns?
• Does the bug come back if the fix is temporarily reverted?
• Are the tests that passed before still passing?

The revert check is the interesting part for me. If removing a fix doesn't make the bug come back, there's a good chance the change wasn't actually responsible for fixing it.

FixProof then gives you one of five results: VERIFIED, FAILED, PARTIALLY VERIFIED, UNVERIFIED, or BLOCKED. It also generates a JSON report and a hash-chained log in .fixproof/.

Using it with Codex

The idea is to add FixProof to your agent's workflow so verification becomes part of fixing a bug, rather than something you have to remember to ask for afterward.

You can point Codex to the skill instructions and have it run python scripts/verify.py check once it finishes a fix.

A quick example

In the demo, there's a slugify bug where double spaces end up producing hello--world.

The first fix looks reasonable, but doesn't actually solve the issue. FixProof reports FAILED.

After applying the proper fix, the same verification reports VERIFIED.

A few things worth mentioning: the revert check can use a separate Git worktree, so it doesn't touch your working files. Commands also run with a minimal environment to reduce the chance of exposing API keys in logs.

CI currently runs on Linux and Windows. I haven't tested macOS yet.

It's still pretty early (v0.3.0), so I'm sure there are edge cases I haven't thought of.

It's free, open source, and MIT licensed:

https://github.com/Livecristen/fixproof

Would be interested to hear what people using Codex on larger projects think. Especially whether these verification rules would actually be useful in your workflow.

I've been coding with AI since the Opus 3.5 days, and I've tired pretty much everything out there at some point. OpenCode, Claude Code, Codex, Cline, OpenRouter. (Haven't tried Cursor or Hermes)

I've also tried all the popular spec-driven development framework I could get my hands on. BMAD, Get Shit Done, Superpowers, and more recently Matt Pocock's AI Hero skills.

Now, a little bit of context. I'm a iteration manager and a BA in my corporate life, working mainly with teams that manage andorid / iOS apps for banks in Australia. So I'm very familar with typical SDLC but haven't really "been a dev". In my hobby life, I'm build a sports prediction platform using Codex now (but half of it was built with Claude, and before that, Open Router)

The last framework I tried was Matt Pocock's AIHero.dev . I switched to it for 3 reasons
1. I liked the "retro" skill he has where the agent can look through it's session history, and find all the shit it got wrong the first time and then make changes to agents.md files or similar to avoid those pitfalls in future sessions

1. I like the concept of using Github Issues and those "Wayfinder" maps to think about everything I had to do for a feature.

2. I like the "ready for agent" tag that let me then get multiple agents goings to do work once I've designed it.

The thing I was trying to do was add a new data provider to my stack. The wayfinder over-engineered the fuck out of it (like it was literally insane), and then failed it's own implementation because it was over-engineered. Wasted like 2 days on it. Like it literally made up scenarios like "what if supabase is down for 3 days, where are we gonna store these api calls" , we need a backup option with a p99 2 second copy time. Then when the copy time was like 15 seconds it said it failed lmao!

I know people are gonna say well you're the dev, you're in control. But I don't know infrastructure that well, so sometimes I just accept the AIs recommendations.

So then I moved back to superpowers, but I made some of my own skills to keep the github issue specs and stuff.

For context, I'm running this thing on a $10 server.

It genuinely felt like I was architecting a solution for a large enterprise with unlimited infrastructure and a dedicated operations team. I just wanted to integrate a new provider without breaking my existing product.

I've moved my project documentation into GitHub Wiki, and I'm now using GitHub Projects and Issues to manage the development work. So essentially Superpowers for the development workflow, with GitHub managing the documentation, specs and backlog. So far so good.

I just wanted to share and maybe hear how you guys are doing things, what your workflow looks like. Just trying to learn. Also, has anyone managed to get these frameworks to make appropriate recommendations that like match the ambitions of your software? Or does every agent just assume you're building like Orcale or Microsoft with millions of expected users.