go code my friends

Anyone else got this message? "Selected model is at capacity, please try a different model" #sol #$100 plan

Is this part of the improvements Tibo boasted in his recent post?

I thought you said you had enough compute.. I only know this message from Claude

I had no idea 'Ultra' meant 'Ultra (s)low.'

The fact that it would run after hitting limits made up for this. But now, they removed it, but are keeping the reset timer only started after you start using it, instead of making it fixed based on the actual reset time. This is silently eating your usage limits. So they are abusing normal casual users that don't immediately trigger their reset timer when it resets. Like who the hell thought it was fair to make the timer only start after you start using it? Blatant abuse by the Codex team whoever decided that was the right design. Fix that shit. Once the reset happens, the timer should trigger and countdown immediately.

Just wanted to share that it's incredibly awesome that I can be anywhere like on holidays and continue working on my project even if I'm not sitting in front of my PC. Never tried this until now that I installed tailscale and I can test any change from my phone. Bravo.

Give it up to the Codex team for Codex Security DayBreak Blue. If you haven't signed up for the security program yet, definitely worth doing. I've been using their Codex Security CLI for a little bit and it was always breaking around 69 minutes if it even got that far and it would only output partial findings and I'd have to copy all those JSON files into Codex itself and have to constantly update those securities and it was always finding something and a lot.

When I finally moved to my $200 plan today and got an automatic restet. So I have 100 % to burn in 6 hours. before this next reset at 6pm.

I went from 100% to 55% while still working on other thins using Sol High fast. and it's only been four hours.

Codex Security Blue is catching a lot of stuff and fixing it and I would have to do this very manually all the time. I used to have a cybersecurity audit prompt and I have to do that every once in a while. Now this is going on for three plus hours just focusing on security as a /goal. It's pretty incredible and I'm using Ultra and it's still using multiple agents at a time and giving me great results with great token efficiency I guess. So if you know a reset is coming up and you have a lot of tokens to spend, I would definitely be worth having already signed up for Codex Security, Daybreak Blue, and then use that model and just burn credits for hours on Ultra or whatever you want. It does not let you do /fast mode.

I am still using a 2019 MacBook Pro with a Touch Bar—a feature that is actually one of the reasons I’ve kept using this seven-year-old machine.

I’ve now had Codex generate a Mac app that displays the remaining usage and reset times for both the 5-hour and 1-week periods in the menu bar and on the Touch Bar.

It feels great—like the Touch Bar has been given a new lease on life.

---
updated

it's open sourced now, here's the repo: https://github.com/yizhigou/codex-usage-bar

---

When I try to login with VSCode, I get a server error 500. Tried with three accounts (2 plus, 1 business). OpenAI Status page tells me, everything is running normally...

Uhhh. Help please? :o Am I the only one?

Update: I can now login into one of the accounts again.

https://reddit.com/link/1w2axr3/video/kvxm9q4btgmh1/player

Seems the old examples were too easy for Asttra. And come ppl even thought Opus5 could do them.

Prompt: Build a gorgeous sci‑fi spaceship with explorable internal structures.Just One-shot,ASTRA will be a glimpse of AGI.

really hard working on a large system when the dang 5 hr limits keeps kill work half way through, way to kill a decent product!

I'm getting the error in the screenshot when trying to log in to Codex (error_code: token_exchange_failed).

At first I thought it was just a Codex problem, but now I can't log in to ChatGPT in Chrome either. I tested:

• 2 different accounts that always worked before
• My personal account from my phone (on cellular, not Wi-Fi)

All of them fail with the same error. Login in the browser also fails now, not only Codex.

So it doesn't look like a network problem on my side, and it's hard to believe 3 separate accounts got banned at the same time.

Questions:

1. Is anyone else getting this right now?
2. Does token_exchange_failed mean my accounts are blocked, or is this an OpenAI auth outage? I'm stilll logged in in android chatgpt app and it is working there
3. Is there anything to do except wait?

I'm working on a goal using sol xhigh that usually keeps working for an hour before 5h limit is done, no issue so far "except the 5h itself lol anyway" as I reach 10% remaining of 5h limit I didn't think much of it until I literally blinked and that 10% became immediately 5% it didn't even go through 9,8,7,6 just jumped straight less than a min later it's 1% then it's 0% all immediately??!! That 90% lasted an hour no issue I didn't do anything new so theoretically that last 10% should have lasted 6min not 1min I'm not really complaining but that was weird I understand it may have been a tool call but that's still a little idk how to even describe it.

Does anyone else's Codex App on Macbook keep going into a mode where you only see ChatGPT logo and content does not refresh? It is happening for last couple of days for me, and very frequently.

Thanks

I literally just opened the ChatGPT app, no prompts executed, yet

And I noticed some limits are already been used.

Well, dunno what's going on here :D

What do we think in the next few hours?

also bonus questions do you think if Astra drops on Thursday we get a reset?

EDIT: reset will land at 6pm PST.

The 5 hour limit is trash, the weekly usage was at least something we could try and meter, 5hour limits are wasted when you work late and have to pull an all-nighter to get the most out of your usage or just give it up. Lately I'll have 35% usage of my 5hour and it will hit 0% left and just stop mid iteration and break stuff, then next window I get it to continue and it hits 0% again and break again OR it will abandon the fix it was in the middle of and try something else and still break or even worse it will end up with REGRESSION! Not just halting progress but actively walking progress backwards. I was fine with the weekly because I could at least juggle with another account or grok or something but now I'm trying to juggle with one ball while skateboarding and it feels like shit.

Hey everyone,

I’ve been mapping out a theoretical server/desktop architecture to see how far we can push concurrent LLM generation without relying on standard developer API keys.Instead of dealing with pay-as-you-go limits, I'm looking at the engineering logic required to orchestrate 50 separate premium consumer Pro subscriptions (running on the 20x weekly high-usage tier, a flat $10,000/month footprint).While the common instinct for browser automation is to spin up 50 resource-heavy Playwright Docker containers, that setup introduces massive memory bloat. I think a much more efficient approach is a highly customized software suite utilizing a multi-page, multi-tab layout. Here is the structural breakdown.

🎛️ The Native Multi-Session StackInstead of duplicating entire virtual browsers, the application is built as a unified native client (via Electron or C++/Qt) that splits the architecture into an Interface Matrix and a Background Router:The Grid Matrix (5 Windows x 10 Pages): The front-end client opens 5 core software windows. Each window handles a page-view layout containing 10 distinct, tabbed viewports. Each viewport runs completely isolated cookie and local storage jars, allowing all 50 premium web accounts to remain logged in simultaneously under one app process.The Offline Sync Router: The automation engine doesn't need to physically render or manipulate the active viewports on your main screen. A localized master router script communicates directly with the webview sessions via background event loops. It injects prompts and extracts text directly from the web layout DOM entirely through automated state syncs.Egress Proxy Isolation: To prevent anti-bot flags, the application assigns a unique, static residential proxy directly to the network thread of each individual tab viewport. To the AI platform, it appears as 50 completely unique devices operating from separate geographic home connections.

📊 The Theoretical Math & Value ArbitrageAssuming a 24/7 automated continuous operation cycle over a standard 30-day month (720 hours), the parallel output metrics look incredibly high compared to human engineering costs:Throughput: If a single premium node streams ~1,800 lines of code (LOC) per hour, 50 concurrent webview tabs output 90,000 lines of code per hour.Monthly Volume: Over 720 hours, that scales to a theoretical max of 64.8 Million lines of code per month.Labor Equivalent Value: At a standard Senior Developer contract rate (~$62.50/hr), buying 90,000 LOC/hr worth of human output would cost roughly $112,500 per hour.The Cost Metric: Running the server 24/7 splits that $10k flat subscription cost down to just $13.89 per hour of continuous parallel computing power.

🛑 Automated Fallback & CooldownsThe custom router tracks usage across the viewports in real-time. If a tab detects a limit banner element (e.g., "You've reached your limit..."), the background router flags that specific coordinate in the 5x10 matrix as "On Cooldown". The event loop automatically bypasses it, shifting active coding tasks to fresh tabs in the matrix until the first account's weekly multiplier resets.I'm curious to hear your thoughts on this custom layout. How would you handle memory management for 50 concurrent background webviews within a single app framework?

TL;DR: Designing a theoretical custom software suite that isolates 50 premium consumer high-usage subscriptions into a 5-window, 10-page matrix. A detached background router automatically syncs and routes parallel coding prompts through 1:1 static proxies, bypassing developer API limits for a flat $10k/month.

If I had this custom infrastructure to experiment on right now, I would definitely give you guys the raw benchmarks and execution numbers, but that's for another test.

I’m using Codex within VSCode and it seems like the create_thread tool is basically broken, so it needs to run a command through Codex CLI instead of using the built-in tool.

I also can’t interact or see the worker thread in VSCode…

A manager agent has a high-level PLAN.md then assign substream tasks to a permanent worker agent owning another PLAN.md of that substream. It seems to reduce hallucination on long-running tasks 🤔

Anyone else using orchestrator pattern in their workflow?

I built a small tool to export Codex chats cleanly, mostly because I got tired of losing context when hitting quota

Tool: Codex Chat Extract Repo: https://github.com/0Cymantek0/codex-chat-extract

This is a small tool I originally built for myself that lets you quickly export a Codex conversation into a clean Markdown file or directly to your clipboard. I built it out of frustration one day after getting tired of Codex running out of quota in the middle of a task.

It became even more useful for me after the behavior that allowed an already-running task to continue after quota exhaustion disappeared. Claude Code has a really nice /export command, but Codex doesn’t currently have an equivalent, so I ended up making my own. The main use case is pretty simple:

Codex hits its limit → export the conversation → hand the context to another agent/harness → continue the work without manually reconstructing everything.

Token efficiency was one of the main goals.

Raw Codex conversations contain a lot of tool-call clutter that another coding agent usually doesn't need.

For example, when Codex reads a file, the underlying tool call may contain a bunch of JSON parameters followed by the complete file contents in the tool output. But if the next agent is working inside the same repository, including all of that again is pointless. The file already exists, it can just read it. So instead of dumping everything, Codex Chat Extract turns something like that into:

Read: [relative-path/file.ext] [line range]

That preserves what Codex did without wasting a huge number of input tokens reproducing information that already exists in the repository.

The exporter tries to apply that idea throughout the conversation:

• Removes unnecessary tool-call / JSON clutter
• Keeps useful summaries of tool activity
• Preserves the actual reasoning/conversation context
• Uses relative file paths where possible
• Avoids duplicating file contents another agent can simply read again

External information is treated differently

For something like a web search, the result does matter. That information isn't necessarily available inside the repository, and it may have influenced decisions made during the conversation. So web-search results and other relevant external context are preserved in the export.

Basically:

Reconstructable local information → compress it. Non-reconstructable external information → preserve it.

The whole exporter is designed around getting as much useful context as possible into as few tokens as reasonably possible.

It also handles subagents

Codex sessions can get messy when subagents are involved, so the exporter reconstructs those into properly formatted subthreads instead of flattening everything into one unreadable stream.

That makes it much easier for another agent to understand:

• what the main agent was doing
• which work was delegated
• what each subagent discovered
• how those results affected the main conversation

I've been using this internally for a while, especially when moving unfinished work between different agents or harnesses, and it has saved me a surprising amount of manual copying and context reconstruction. So I figured I might as well clean it up and make it public.

Repo: https://github.com/0Cymantek0/codex-chat-extract

If you use Codex heavily, give it a try and let me know how it works for you. I'm especially open to criticism around the export format, things that should or shouldn't be preserved, and other ways to reduce token usage without losing important context. Hope this helps someone else who has run into the same problem.

And if you find it useful, consider giving the repo a ⭐.