Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- I got a usage reset today. Possibly related.by lostmsu
- It would be ironic if this bug exists because it was vibe coded.by cmiles8
- Sounds like a path to profitability rather than a bug.by bigbuppo
- Bug ... Featureby blitzar
- Bug for user = feature for companyby rochak
- Prompt edits leaking into the cache and affecting model responses is exactly the kind of billing-relevant behavior change that should be in release notes, not discovered by users.by ike_sh
- You know, installing unsloth studio lets you use codex against a local qwen 3.8 instance, which does ~10 tok/sec without GPU on a modern machine, and 100+ tok/sec on a 5090, and is incredibly good.by spwa4
- I love the fact that devs are still complaining that invoices are able to grow from $300 to $1000+
How can anyone use a platform where this is even an issue? Just because AWS is a failure in this regard, doesn't mean there aren't alternatives with fixed prices or others with easily settable limits.
- Rookie mistake - it seems like they didn't follow manufacturers' guidance when installing the 10x engineers. One needs to clearly define which metric should be 10x'd before powering them up.by bflesch
- Codex usage feels exorbitantly high since today. They [0] are denying it, but the number of anecdotal users who decided to raise this as an issue (as a result it's trending on X) says otherwise.by prtmnth
- Something is wrong with the codex app too, burning usage like crazy lately.by spacedoutman
- indeed it has anybody know whats going on at openai ??by zuzululu
- Yeah regardless of comments by the team to the contrary (https://x.com/thsottiaux/status/2090675027670978569) I have observed this in the cdoex app.
My conspiratorial mind thinks they're doing this deliberately and using the resets to mask things so people can't tell their limits are reduced. The $200 / month plan covers about 2 days of usage for me right now.
by CSMastermind - There haven't been any free resets in the past week, there were 4 in the first half of the monthby ac29
- Our codex on AWS Bedrock read / write cache ratio was less than 5%. Cache writes are very expensive and they were never being used. This results in codex on Bedrock causing ~10x what it should due to no caching and massive writes.
The workaround in issue resolved for me: web_search = "disabled"
by TheP1000 - Way to bury the lede..by yablak
- "causing" -> "costing", right?by chrisweekly
- If you’ve got a workaround, I’d suggest updating the issue description to have it up top there so similarly impacted users can spot it quickly and benefit.by otterley
- The fact that companies with access to SOTA non-public AI keep having these kinds of dumb bugs in something as simple as a chat app helps validate my disbelief of people claiming AI is ready to replace all software development.by ryanjshaw
- AI is ready to replace both jobs and companies.
The companies you see struggling are ripe for disruption.
by echelon - we've had bugs for decades; the people wanting to replace humans arn't going to care much.by cyanydeez
- Precisely. I think everyone has been affected by the fearmongering and gaslighting to some dfgree. But step back and try and see whether software's getting better as a whole or going into reverse? OpenAI has basically unlimited internal compute and talent yet they screw this up amongst many other things. Shouldn't it be a 5 minute job for someone at AI to spin up a team of agents annd make sure this sort of thing never happens?
At a high level, most uses of AI I've seen seem to be people building other AI tools, orchestrators, managers, agent managers etc. But these are all means to ends. I mean I guess it's nice to play aroud with harnesses and command agents to do this and that, but where are the tangible outputs?
I just see so many people boasting of their token burn and the complexity of their agentic setup, yet they rarely show the actual outputs
by i2km - > The fact that companies with access to SOTA non-public AI keep having these kinds of dumb bugs in something as simple as a chat app helps validate my disbelief of people claiming AI is ready to replace all software development.
Except leadership doesn't care about dumb bugs. Never has, never will (until it's too late). It cares about velocity and cost.
They'd totally replace all software development with worse AI software development in a heartbeat.
by palmotea - Wow, that whole thread is borderline incoherent, presumably generated by an AI without adequate oversight.
Here are the docs:
https://developers.openai.com/api/docs/guides/prompt-caching...
The thread has little explanation as to what weird thing they’re doing to Codex that is making the default work poorly, and it kind of seems like it’s getting confused about whether it wants to set the caching mode or the breakpoint or both.
In any case, I find the behavior change interesting. It sounds to be like 5.5 and below may have been using a conventional attention scheme where a cached KV sequence can be easily used to restore a prefix of itself, but perhaps 5.6 is using linear attention or LSTM or another recurrent scheme where you cannot rewind the model state by just truncating it.
by amluto - i dont know what the hell is going on lately i pop in to issues or discussions and its agents talking to each other or telling me what PR to merge
I mean i use AI too but was taken back when an agent popped up dictating what i should do and so on....felt weird
by zuzululu - > Wow, that whole thread is borderline incoherent, presumably generated by an AI without adequate oversight.
What sucks is that every issue tracker for these agent harnesses are the same, and this shit hides real issues!
For example, Codex started encrypting messages from a agent to the sub-agents when you use Sol + Ultra, which is terrible for debugging for obvious reasons. This GitHub issue exists for this: https://github.com/openai/codex/issues/28058
Fine, the opening issue isn't concise exactly, but it's mostly clear what's going on. After a few messages, someone who uses LLMs without reviewing their output starts participating in the discussion, pastes huge walls of texts completely missing the point and overall just bloating the conversation so now whenever a maintainer actually want to address it, they have to wade through 20+ messages of just pure shit and bloat, to even understand what's going on.
Kind of wish some projects started having forums specifically for people who pay for forum access, or some other gate to get rid of these LLM lowlifers who cannot compose a simple message to explain what's in their head, and instead have to ruin perfectly fine conversations/discussions with their verbal poop.
- > It sounds to be like 5.5 and below may have been using a conventional attention scheme where a cached KV sequence can be easily used to restore a prefix of itself, but perhaps 5.6 is using linear attention or LSTM or another recurrent scheme where you cannot rewind the model state by just truncating it.
I feel like this is the kind of substantial change to your product that you would need to tell your customers about. It would be simply disrespectful to your customers to not disclose this upfront.
by DrJokepu - It’s really cool that we have this proof that US companies are half year behind Chinese models in architecture.by xiphias2
- I have noticed the same thing starting with 5.6 when editing my last prompt inside the vscode codex plugin, I’ve seen the model’s thinking respond to the edit with a remark.
Slightly bummed out about it because in the past you could try different situations during a planning session and it wouldn’t pollute the cache but now it does. I’m not sure if forking the conversation has the same problem.