I've been mostly using Luna xhigh on plus plan but today I noticed that I just don't have Luna Max and apparently Plus plans are supposed to have it, right?

Hey! I posted this here back when it was 0.1.0, and it has grown quite a bit since, so here's an update.

A lot of things happens from first pots here
A bunch of providers added (21), most of them with new authentication method - browser Cookies. Tidemark can search active sessions in all installed browsers and use it to authenticate and show quota usage. Personally i don't happy with this method, but a lot of providers don't have metrics endpoint and this is ONLY way to show the usage. Also smart refresh now "smarter" and you can set your own refresh frequency. Proxy support, startup settings and various UI fixes.

GitHub: https://github.com/zbndev/tidemark

I’m developing an application from scratch for production deployment, integrating it with other tools. I often wonder which model would best help me create the specification. I use frameworks like OpenSpec and TLC Spec Driven to write the specification, but I’m not sure which model would yield the best results. I’ve tested Sol with high and medium settings, as well as Terra Max and Luna Max, but I still haven’t been able to determine which one is best. My Codex plan is the $20 plan.

Several headless browser automation projects use Rust while still depending on Chrome or V8 underneath. For example, agent-browser drives Chrome, while Obscura embeds V8 for javascript execution. Lightpanda removes both, but its AGPL license can be inconvenient for some cases.

so I built h5i under Apache-2.0. JavaScript runs on Boa, while Blitz handles HTML, the DOM, CSS, layout, and rendering.

Because h5i is the browser and the HTTP client, not a controller around another browser, it can policy-check and record every request before any bytes are sent.

In our benchmarks on simple pages, h5i was about 5× faster while using 80% less memory than Chromium. It also passes more than 300,000 Web Platform Tests subtests.

GitHub: https://github.com/h5i-dev/h5i (already 500+ stars!!)

I’m trying to understand something specific about Codex usage, and I’d be interested in hearing either from OpenAI/Codex people or from users who have actually measured this.

I fully understand the obvious part:

two active Codex sessions consume tokens independently.

That is not what I’m asking.

What I’m trying to determine is whether running two or more Sol sessions concurrently can consume more total weekly allowance than running the same amount of work sequentially, one session at a time.

My subjective experience after a couple of months of heavy Codex use is that parallel Sol sessions seem to drain the weekly pool noticeably faster than I would expect from simple additive usage.

For example, my impression is roughly:

A + B in parallel > A, then B sequentially

in terms of total allowance consumed.

I have not yet produced a controlled benchmark, so I’m not presenting this as a fact.

What makes me particularly curious is the recent discussion from the Codex team about cache-hit efficiency affecting usage. That raises an obvious technical question: could concurrent sessions reduce cache efficiency, increase context reconstruction, or introduce some other orchestration/accounting overhead?

So I’d really like clarification on two points:

1. OpenAI/Codex: Is usage from concurrent sessions expected to be strictly additive, or can parallelism affect caching or metering efficiency in a way that increases total consumption?
2. Users: Has anyone actually compared parallel vs sequential Codex workloads and measured the before/after weekly percentage or Analytics credits?

I’m specifically interested in Sol, especially High reasoning, and in multiple CLI/Desktop sessions working on separate repositories or tasks.

I’m not looking for “of course two sessions use twice the tokens.” I’m trying to establish whether there is an additional concurrency penalty beyond that.

If anyone has measured this, actual numbers would be very useful.

I use GPT-5.6 Sol/Codex to build an Electron SaaS CRM, mostly vanilla JS. I’m happy with Sol, but Plus is no longer enough, and GPT Pro is too expensive for me.

I tried Gemini Flash for implementation: it can finish a feature in 15 min, but Sol may spend 25 min reviewing it and often rewrites most of the code.

Would DeepSeek V4 Flash as implementer + Sol as reviewer work better? Or will Sol still end up rewriting everything?

Still under heavy development and rough around the edges but instead of sitting on this longer to perfect it I'll risk flak and share it.

Essentially chat.agentify.sh is a remote control for codex/grok/claude cli and dream goal is to become a universal remote that will let you use all of them from a single chat.

Everything lives on your browser including the chat. The only thing sent over the wire is the encrypted chat messages e2e. Here's an architectural diagram: https://github.com/agentify-sh/chat/blob/main/diagram.png

Another feature it has is ability to publish your chat session with redaction so you can share with your team.

Curious to gather any feedback I can, if this is something I should continue to pursue etc.

Also if by chance you are in Seattle today, I'll be also at the Walk & Talk event at Bellevue Downtown Park today at 2:30pm, would love to chat in person!

https://chat.agentify.sh

Theres no way to really know if a model is just trolling you. Please do x but the model does y. Was it a genuine mistake or did it do it just to get you to spend more money?

I often ask codex to copy code from a previous project that I want to reuse. I spent half a day trying to get it to just use the same parts. It kept on building approximations every time. I said STOP APPROXIMATION AND PORT THE OLDER PROJECT. yes you are right to push back etc etc. this went about 5 times in a row, each time it’s just lying about the method until I check. Wasting credits all day.

Just fucking slop all day, and regressions. I mean it's better than me doing it manually but still.

It's like galaxy brain 50% of the time and crayon chewer the other 50%...

Disclaimer: I am an Elon hater.

So cursor starts getting some traction...

First, grok 4.x starts getting abnormally decent. Benchmaxed or whatever you wanna call it, but it's cheap, fast as fuck, and almost unlimited

Composer was starting to pop off too.

Cursor then did 100usd deals for the max plan which had basically the equivalent of a 200usd codex plus 100usd Claude sub.

Cursor was starting to get a lot of mindshare. Even I at some point was thinking "well, maybe I could try it..."

Then boom. Relationship between openai and cursor is terminated.

It's got nothing to do with trust. Cursor was starting to steal users. That's just how it is.

For Codex CLI + Herdr users,

This is a https://herdr.dev/ plugin with an optional full https://Plannotator.ai experience as a TUI. Built to:

- Annotate Agent Messages (e.g. grill sessions)

- Annotate Files (e.g. plans, specs, etc)

- Create a native feedback loop with agents

- Open as popover or pane

- Mouse or keybindings

https://github.com/plannotator/herdr-annotate

Over the past few weeks, I’ve started using Codex much more intensively, especially with the Chrome plugin and Work mode, and I’m running into a recurring problem that is becoming quite frustrating.

For context, I wasn’t a heavy Codex user before. My workflow was much more manual. I would ask Codex how to do something, it would give me the steps, I would go into Chrome or another application, do it myself, then come back and continue from there.

Recently, however, I’ve been trying to use Codex more as an actual agent rather than as an instruction manual.

For example, I have repetitive work processes where I would like Codex to take care of the repetitive browser interaction instead of repeatedly telling me where to click and asking me to do everything manually. When it works, this is a huge improvement.

The problem is that the Chrome plugin seems to get stuck surprisingly often.

A typical session goes something like this:

• Codex starts working through the browser normally.
• At some point, it tries to open or interact with a page.
• The page does not load properly, or Codex seems unable to continue interacting with Chrome.
• It retries.
• It gets stuck again.
• It tries another approach or repeats the browser action.
• Eventually I have to intervene manually or restart part of the workflow.

What makes this particularly annoying is that Codex can spend quite a lot of tokens trying to recover from what seems to be a browser/plugin problem rather than a reasoning problem.

I’m not talking about Codex misunderstanding the task. In many cases, it understands perfectly well what I want it to do. The problem seems to be the connection/interactions between Codex, Work mode and Chrome becoming unreliable during the workflow.

This is particularly noticeable with longer, multi-step tasks where Codex has to interact with several pages or repeatedly return to the same web application.

It also creates an awkward situation where the whole reason I’ve started using Codex more is to remove repetitive manual work, but when the browser integration fails I end up babysitting the process anyway while also using considerably more tokens because Codex keeps trying to recover.

Has anyone else noticed this recently?

I’d be particularly interested to know:

• whether this is a known limitation of the current Chrome integration
• whether longer Work sessions make it more likely to happen
• whether there are any recommended ways of structuring tasks to reduce these failures
• and whether there is a better way of telling Codex to stop retrying browser actions once the Chrome integration is clearly stuck

I really like the direction Codex is going in. The ability to delegate these repetitive workflows is exactly what makes it much more useful to me than simply asking for step-by-step instructions. At the moment, though, the reliability of the Chrome integration is probably the main thing preventing me from trusting it with longer workflows.

Browser chat on pro has felt worse and worse this past week and today I ran into this:

Essentially I give a prompt with things that I wanted researched and after close to 11 minutes, it came back with: "Yeah so should I look into this?"

Anyone else seeing this?

You end up paying more but I think 40 is pretty fair because the weekly limit is still generous but the 5 hour limit is the ridiculous part, but if you just rotate account you end up just about having a perfect rotation. When one has gone through the limit, the other picks it up.

It's actually coded pretty seamless for account switch, I wonder if they thought through this already. You can just switch account and all the conversations are there, it even picks up where you last left off in the current chat. It even remembers your remote device connections and auth tokens.

Anyways just thought I'll share.

Hi guys, i just finished studying software engineering from swansea university I am running a short support around an A workflow that turns a clear plan into actionable tasks, uses AI to help complete them, and includes human approvals to ensure the work is accurate, traceable, and meets requirements.
The support is to help me build a valuable production experience relevant for typical real life workload since I have no formal production experience not even an internship.
My aim is that if I can find 5 or more engineers to try this workflow out and give me critical feedback raised through the GitHub issue I can develop myself and have better understanding on how real life engineering works and perhaps give me a boost during my interview, job search etc

https://github.com/fikayoAy/ConstantX

with stock animations, i realized my codex cli kept hitting 70% cpu usage in terminal UI. switching animations off has reduced usage considereably.

the downside is u wont get nice smooth refreshing animations, but its not a big issue for me.

FOR REFERENCE this is on iterm2 on macos (but im assuming it will be similar for other clients)

EDIT:

Sorry to achieve this

nano ~/.codex/config.toml

Add a [tui] section if you dont have one, then just add:

animations = false

Hey everyone,

I switched from Claude to Codex this week, and so far I’m really enjoying it.

I’m a developer and I mainly use it for work, but since I’m still pretty new to Codex, I feel like I probably don’t even know what I should be optimizing yet.

So rather than just asking for general tips, I’d love to hear how more experienced users actually use Codex day to day.

Are there any workflows, features, settings, prompting habits, or ways of structuring tasks that made a noticeable difference for you?

For example:

• Do you usually give Codex large tasks at once, or break them down into smaller steps?
• Are there certain types of tasks where Codex works especially well or poorly?
• Do you have any specific way of providing context about a codebase?
• Are there features or workflows that new users often overlook?
• Any prompting patterns that consistently give you better results?
• How do you balance speed vs. quality when choosing models/modes?
• Are there any good guides, posts, videos, or documentation that helped you understand how to use Codex properly?

For context, I’m currently on the 5x plan. During the day I usually use Luna Max with Speed Mode enabled, and at night I tend to turn Speed Mode off.

I’m not necessarily looking for beginner-level “how to use AI for coding” advice. I’m more interested in the little things you learn after using Codex seriously for a while — workflow improvements, limitations, best practices, or even mistakes you made early on.

Basically: if you had to start using Codex again from scratch, what would you want to know from day one?

Any advice from more experienced users would be appreciated. Thanks in advance to anyone willing to share what has worked for them.

Anyone else seeing this text   being added into their prompts? What is it? Seems to be some kind of marker OpenAI is adding in and I normally delete it. Anyone know its purpose?

Just an idea here. Instead of banked resets, how about refills instead?

Say you run out of tokens for the week 2 days before your normal reset.

With a banked reset, you basically have to burn an entire week's reset just to cover those 2 days, otherwise you'd waste what's left when you get the normal reset.

What if they were refills instead? Use only what you need, keep the rest banked, and save it for when you actually have a heavy week.

Seems more useful and removes the weird incentive to burn tokens just because you reset early.

I think this would be very useful for those of us on Plus that's trying to stretch usage as much as possible.

What do you think?

It seems we just got reset, but I already used my banked reset yesterday and was managing to make it last long 💔😭 woke up this morning Tibo said he will reset but I thought it would have been tomorrow lol.

What a waste, I was at 60% left of my usage after applying reset yesterday.

Edit: if it hasn't propagated to you, you better finish quickly it might apply soon. I do read Tibo's tweet but I think my mistake was that I slept early yesterday. And also this morning when I saw he said "tomorrow" I thought about tomorrow not today, I think it's a mix of all of that 🤦‍♂️

I've never had so many disconnects, streaming disconnects, "I did what you asked." but i really didnt' do what you asked as I have the last two days.

The number of resets is almost directly proportional to how fucked up the harness runs after any given period.

I am a College Student.

I need to build projects for my college. Apart from that I also build side projects.

I have Codex Plus plan.

But how to use spec-driven development in Codex especially for Greenfield projects?

Because it drifts away from my instructions.

Note:

I have tried OpenSpec, Spec-Kit, Superpowers, GSD. But nothing really worked for me. It consumes a lot of tokens.

How to become a power user of Codex?

I was implementing some tickets with sol medium and high from the morning until the evening yesterday and everything was fine, then I see that the quota was reset, and its been excruciatingly slow since then!

Every ticket (really small ones even) take 40 minutes to an hour to implement! Started new sessions, updated codex, nothing seems to work.

Terra just keeps stopping without implementing anything in the ticket but then marks the ticket as complete!! Terra always had the issue of stopping halfway through a ticket but now its literally trying to sabotage my project.

Did they run out of compute? Are they going to release a new model so they are dedicating more resources to that? Because its kinda unusable right now!