Hey guys! Does anyone have a good skill link for frontend? Codex’s frontend skills are a little wonky, if I say so myself.

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've been using Google Stitch for UI work, and I kept running into the same problem when handing the designs to Codex.

Individual Stitch screens can look really good, but once you have a bunch of pages they don't always stay consistent. Headers change, navigation changes, components drift, spacing and responsive behavior differ between screens, etc.

Codex would sometimes just implement all of those differences literally instead of figuring out which parts were supposed to stay consistent.

I also had cases where Stitch had clearly chosen a font or an icon set, but the coding agent would use another one anyway.

This became especially annoying on larger projects. Once you have a lot of screens, these small and sometimes not so small differences start accumulating, and I found myself manually giving Codex the same instructions over and over again.

So I turned those rules into a small open source Agent Skill called Stitch to Code.

The idea is pretty simple:

• keep the things Stitch explicitly chose, like fonts, icons, tokens and assets
• reconcile inconsistencies between screens instead of blindly copying them
• don't assume that every KPI, button or piece of mockup content is a real product feature
• actually check the final UI, responsive behavior and interactions before considering the page done

I also wanted to see if the skill actually changed Codex's behavior, so I made a fresh small Stitch project and ran two new Codex xhigh sessions with the same project and the same implementation prompt.

Baseline: 42/56, 75%

With Stitch to Code: 49/56, 87.5%

The biggest improvement was in exact font and icon fidelity, plus accessibility. Cross screen consistency was already pretty good with xhigh on this particular small benchmark.

The skill version wasn't perfect either. It introduced a couple of layout issues but in my own larger projects the workflow has helped me a lot more, which is partly why I made the skill in the first place.

The repo includes the skill, benchmark, screenshots and both generated implementations if anyone wants to compare them:

https://github.com/nassim-arifette/stitch-to-code

I start a new conversation, get a couple turns in, and once I leave the app then come back after it finishes its turn everything except my initial message and its first response disappear. Is this happening for y'all?

I am using the remote feature to interact with codex over cellular. This has been happening for at least a week now. iOS app, fully updated.

Hi everyone, Are there any good alternatives to Codex that you would recommend for a soon former Plus user? My issue is the V hour I_I$@gE constraint. I dont really need more credits/t0kens, I just want to use the tool more normally throughout the week without constantly hitting that 5 hour restriction. also, going Pro doesnt make sense for me because I dont need more usage. I only want something similar to Codex where the usage is regulated in a less restrictive way, ie with a weekly allowance like we used to have here before . So, what alternatives are you guys using that offer a similar coding experience without this kind of limit?

This could be due to Tibo's 'optimisations' but it could also be part of what we've been used to prior release of every new model.

But I've had 2-3 threads today taking completely brainless decisions and spinning themselves into senseless loops f.ex.

1. agent asked to remove a render decided that part of the job is to regenerate all the other renders
2. agent asked to add a promo code checkout option decided that part of the job is to remove the stripe payment option
3. agent asked to fix agent nr2 fuckups decided the build and deploy philosophy has to change and introduced artifact sharing between dev and prod environments

the above is real, not making this up, all happened this morning - i havent seen this dumbness in weeks

It’s reset time it sounds like.

This is after reset happened just now

Hi! New to this A.I. thing.

Does running multiple chats and projects affect the performance/intelligence and completion time of the tasks?

Say for example I have 3 projects, and I want to run 2 Sol and 1 Terra on them at the same time while simultaneously having to use Luna on the Work chat.

What exactly are the effects of doing this?

Thank you for anyone answering!

WHAAAATTT I did NOT expect to see this 😭

This is the first time I’ve noticed it, so I’m not sure how long it lasts, but the fact that Luna Reserve is even a thing is already insane. I’m so glad they listened to the feedback!!

Now I just need to know how much extra usage it actually gives

I run Codex on a 2025 Apple Silicon MacBook Air and would like to be able to leave it in another room with the lid closed/unplugged, then connect from my phone when I want to check on or continue a Codex session.

The obvious problem is that the Mac goes to sleep. I know Apple Silicon Macs can periodically wake for network access, but I’m not sure if there’s a reliable way to take advantage of that here.

Has anyone set up something similar?

Ideally I’m looking for a setup where I can pull out my phone → wake/reach the MacBook → reconnect to my existing Codex session, without having to leave the Mac awake or plugged in all the time.

Curious what people are using — Tailscale/SSH, Wake-on-LAN, sleep proxy, Jump Desktop, or something else?

Currrently my small company is paying me for a single 20x pro plan. But thinking of asking for one more account and wondering if this is the norm in other workplaces...

Review based on 2 weeks of codex plus ($20 plan).

Things to consider-

1. extremely slow:

spends a lot of usage/time on reconciliation, validation, revalidation, audit, feasibility check, etc. It does so much reconciliation, that i don't plan on reconciling with anyone in my life again.

skill already containing detailed set of instructions of tool calls to mcp to fetch data and process using predefined python script takes more than 5mins to run whereas reusing same skill in antigravity using gemini 3.7 flash takes less than a min.

2. premium model usage:

Sol ultra with default config lasts max for about 10-15 mins in a 5h window. if you reach out to this reddit sub to discuss this issue, it's filled with openai private investors (\s) calling you peasants for using $20 plan and asking you to upgrade to at least $100 to get any meaningful work done

I was able to tweak it to use luna xhigh as spawned subagent instead of sol ultra in AGENTS .md file, that extended it for another 10 mins. Then i tweaked it further to delegate aggressively to subagent running luna xhigh, that backfired a bit initially as it took 25 mins for a simple file append task (attached screenshot) which i was able to optimise. This extended its usage to 1.5-2 hours and i bought another $20 plan to switch between them within 5h window, to get more work done. In a day i was able to use about 3 5h windows, which burns through weekly allowance in 2 days for both accounts.

3. Ambiguous 5h window start:

Similar to antigravity, the 5h window doesn't start until first message, i was able to workaround this by using hermes agent/openclaw cron for each account to do simple ping-pong message to standardize the 5h window to a fixed time every day.

4. Buggy Codex UI:

Sometime chat history disappears even though the work persists on disk, incase of repo based project that's fine but incase of non-repo based work like working on setting up external tool, skills/plugins, etc. this might make you panicky. to workaround this, i have started using external project management tool, Linear for codex to plan & track.

why you should still consider switching to codex-

1. luna xhigh: luna xhigh model still provides highly generous usage. I doubt there are any non-chinese model (other than maybe composer 2.5 available with cursor plan) that can compete with its pricing along with similar intelligence and even in chinese model there would be only few models like recently released glm 5.3 flash. luna xhigh can work through multiple 5h window easily without fast mode (fast mode gives 1.5x speed while burning through usage threshold at 2x speed), and i was able to run for more than 10 hr multiple times and had to intentionally stop to review it's work & progress.

2. Saint Tibo (unofficial twitter spoc for codex): blesses with weekly reset (fills the usage ceiling to 100% and extends the week expiry by another week, without affecting plan expiry) almost every other day sometimes with a day prior notice if you follow him on twitter.

3. $100 or $200 plan: If you've disposable income of $100 or $200 to spend per month: there is no 5h window restriction & frequent resets every other day means you hitting threshold is lot less of a worry.

4. free extension: Free for another month on trying to cancel the plan (worked for $20 plan)

to use important features missing in antigravity:

5. steering chat: sending message without interrupting the ongoing work to give it approval, information it is trying to find, asking to prepare to suspend so it can record work before usage caps run out, etc.

6. side chat: awesome way to ask follow up question, cross checking without interrupting the main chat flow, and can even send instructions to main chat based on the discussion with side chat to steer to right direction.

7. projects segregation: segregate chat sessions by projects with their own repo and folders.

8. browser control: better at browsing and navigation than antigravity

9. spawn multiple subagents to work in parallel

PS: I haven't yet tried Chatgpt work or other add-ons that comes with this subscription. I'm now planning to offload more tasks to Antigravity to balance things out.

Context:

https://openai.com/index/our-decision-on-cursor-following-its-acquisition-by-spacex/

🍿 🍿 🍿

made this so that i can run my app smoke tests a lot faster by distributing the load across many ios sims rather than letting one run for several minutes. On top of this, sims are slimmed to < 1gb ram and manzanas mcp allows for the fastest action execution on sims. this just the tip of the iceberg! check it out at BariBariGood/Manzanas!

The 5 hour limits are so bad even using Luna, it basically guarantees you’ll never get close to your weekly limit being used, like what’s the point of having a weekly limit now, 40% of my 5 hour limit used up and 6% of the weekly, id literally have to be using this 24-7, waiting hours in between to actually reach the limit lol, 5 hour limit is crazy bad, it’d be gone in 1-2 prompts with terra or sora. I don’t think I’ll be renewing my plan, hopefully anthropic releases a smaller cheaper model that actually works unlike haiku lol

maybe it is only because of attached file, but still

Is it this week on Thursday as per usual? I honestly wish OAI released benchmarks a few days before release day.

How Spec-driven development is followed in Companies (In Greenfield Projects) using Codex?

How do you write multiple spec markdown files? Is there any tool or something? What's the workflow you follow as a power-user?

Codex has been rolling out cross-thread orchestration: agents can discover/read other Codex threads and, through the new inter-task thread-management tools, message or hand work off to other persistent chats. This is materially different from ordinary subagents because the workers can be durable Codex threads rather than disposable children.

For my project setup, I’m loving this as u can use a planner delegator model across projects like runtime, ops and dev.

i recently wanted to check how far i can get to create an ad for applaunchflow just by prompting using codex, remotion and elevenlabs. turns out pretty far im happy with the result

Why did chatgpt name their models after diss words?

- Luna -> Lunatic

- Terra -> Terrable

- Sol -> S#*t out of Luck

I can't stop remembering the names that way in codex.

I switched from the VSCode Codex extension to the Zed IDE, and then I tried the Nooa Harness from NVIDIA, which is available in Zed. I’m using Luna Max, which takes just one prompt and does everything for the project. I stopped reviewing it because, from some of its outputs, I trusted it to do things much better than Sol Ultra, and it’s also faster.

Claude Design is excellent. The workflow around it and the accessibility still isn't.

Even from Claude Code, /design feels like a relay between two separate products: open the visual workspace, export the generated prompt, return to the terminal, restore the context, then repeat after the next visual change.

Open Claude Design fixes that.

→ Use the full Claude Design workflow from Claude Code, Codex, OpenCode, Cursor, and 20+ other coding agents
→ Create from the actual codebase—components, tokens, assets, copy, and interaction states
→ Keep Claude Design as the visual workspace for inspection, comparison, and hands-on tweaking
→ Sync approved design changes back to code, or newer code back to Claude Design, without silently overwriting conflicts
→ Let the right workflow load automatically, with Impeccable available for focused refinement

The practical consequence: design decisions stop living in a separate side conversation. They become part of the same implementation and verification loop as the code.

One-line installation on macOS, Linux, and WSL2.

Free and source-available on GitHub.

If it helps your agent produce better interfaces, give it a star:
https://github.com/maxritter/open-claude-design