Remix.run Logo
Codex on AWS bedrock bug causing 10x charges(github.com)
133 points by TheP1000 7 hours ago | 47 comments
amluto 5 hours ago | parent | next [-]

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.

fakwandi_priv 3 hours ago | parent | next [-]

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.

xiphias2 5 hours ago | parent | prev | next [-]

It’s really cool that we have this proof that US companies are half year behind Chinese models in architecture.

weird-eye-issue 2 hours ago | parent | next [-]

Then why are they (US frontier models) still so far ahead whenever I test them against the latest Chinese models? No bias here, I'd love them to be better for my own personal gain, but I haven't seen it

regularfry an hour ago | parent [-]

Behind on architecture, ahead on training? It seemed pretty obvious to me that the opus 4.7 and 4.8 releases were more about trying to retain 4.6-level capabilities while being cheaper to run, which would fit. And they can burn so much money on training.

weird-eye-issue 42 minutes ago | parent [-]

I don't know I just care about the end result. And yeah what you're mentioning here is a pretty common conspiracy theory but you don't actually have any insight into that do you?

geysersam 4 hours ago | parent | prev | next [-]

What is the proof?

cma 3 hours ago | parent | prev [-]

Nemotron was using hybrid with recurrence via mamba layers since around April 2025.

DrJokepu 5 hours ago | parent | prev | next [-]

> 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.

zx8080 5 hours ago | parent [-]

It depends on who they consider the customers. Shareholders and govt are the customers, not users.

Users is the product.

thatguymike 2 hours ago | parent [-]

“Users are the product” is a phrase used when the users aren’t the ones paying for a free service. For a paid API the users absolutely are the customers.

zuzululu 5 hours ago | parent | prev [-]

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

debugnik 3 hours ago | parent [-]

My most awkward experience was a maintainer commenting on my feature request just to prompt a bot to "explain to issue reporter why this is very hard to implement."

It felt like they were trying to avoid me. They could have simply addressed me and given me the explanation they gave to the bot: it would have been simpler for him and more polite. I did in fact reply without waiting for the bot.

squigz 3 hours ago | parent [-]

It's as though you're talking to someone and they were said to their 'assistant', "Explain this to this person" and walked away. It doesn't really matter what the explanation is, it's just gross.

ryanjshaw 4 hours ago | parent | prev | next [-]

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.

i2km 17 minutes ago | parent | next [-]

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

palmotea 3 hours ago | parent | prev | next [-]

> 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.

germandiago 2 hours ago | parent [-]

> Except leadership doesn't care about dumb bugs. Never has, never will (until it's too late). It cares about velocity and cost.

This is the very moment at which I started my own business. I prefer to work for myself with some quality standards than to be in a rush in front of a prompt (not that I do not use AI at all, I do, but not for generating code most of the time).

I knew the future, at that time was basically: pressure for speed, taking ownership of course, even if they rush you. Wild-guess, probably with an AI, to add on top more trch debt. Make everything unmaintainable in the long term.

So this was the perfect moment to show that things can be done in another way and quality can be kept higher than the competition bc what I am seeing lately is people throwing things in a rush. Better twopieces of well-crafted software than 10 pieces of unmantainable junk.

echelon 4 hours ago | parent | prev [-]

AI is ready to replace both jobs and companies.

The companies you see struggling are ripe for disruption.

remoroid 4 hours ago | parent [-]

So OpenAI the company making the AI and using it inhouse is ripe for disruption? What?

dozerly 3 hours ago | parent [-]

I want some of what he’s having please

TheP1000 7 hours ago | parent | prev | next [-]

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"

otterley 6 hours ago | parent | next [-]

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.

the_duke 5 hours ago | parent [-]

It's already mentioned in the issue...

otterley 4 hours ago | parent [-]

It’s in a comment halfway down the page. It’s not in the issue description.

If enough comments are added to the discussion, it might end up being collapsed.

chrisweekly 5 hours ago | parent | prev | next [-]

"causing" -> "costing", right?

vorticalbox an hour ago | parent [-]

In this case yeah. If it’s not reading the cache then it has to compute all the context window again and not just the newest tokens.

yablak 5 hours ago | parent | prev [-]

Way to bury the lede..

ike_sh an hour ago | parent | prev | next [-]

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.

prtmnth 2 hours ago | parent | prev | next [-]

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.

[0] https://x.com/thsottiaux/status/2090675027670978569

i2km 10 minutes ago | parent | prev | next [-]

But but according to Mr Altman, we've like entered the singularity. Right? Who cares about a billing issue?

spacedoutman 5 hours ago | parent | prev | next [-]

Something is wrong with the codex app too, burning usage like crazy lately.

ac29 5 hours ago | parent | next [-]

There haven't been any free resets in the past week, there were 4 in the first half of the month

CSMastermind 3 hours ago | parent | prev | next [-]

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.

zuzululu 5 hours ago | parent | prev [-]

indeed it has anybody know whats going on at openai ??

dgellow 4 hours ago | parent [-]

Maybe preparing for their IPO?

bigbuppo 3 hours ago | parent | prev | next [-]

Sounds like a path to profitability rather than a bug.

rochak 2 hours ago | parent | next [-]

Bug for user = feature for company

blitzar 2 hours ago | parent | prev [-]

Bug ... Feature

bflesch 2 hours ago | parent | prev | next [-]

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.

hk1337 5 hours ago | parent | prev | next [-]

I wonder if it's related to Codex wearing out SSDs.

edoceo 6 hours ago | parent | prev | next [-]

Loaded question: would an openrouter or similar solution caught this before the $BigProblem showed up?

moralestapia 4 hours ago | parent | prev [-]

Funny how it is always more charges but never less or no charges.

"Random" accidents that always go against you, too biased to be random.

But don't notice that too much, you might start to see patterns here and there that you're not allowed to, might get you banned from places, etc.

catlifeonmars 3 hours ago | parent | next [-]

Applying Occam’s razor, which do you think is more likely:

1. OpenAI intentionally adds random overcharges. 2. OpenAI deprioritizes fixing actual bugs that cause occasional overcharges because doing so won’t affect their bottom line.

varjag 3 hours ago | parent | prev | next [-]

This can be a reporting bias. Noone opens an issue when they were billed too low.

andrewchambers 3 hours ago | parent | prev [-]

I doubt anyone announces when they have under billed. OpenAI has also done many low price deals and quota resets.

evalystai an hour ago | parent [-]

Usually it's user's incentive to control over-billing and company's one to make sure there's no under-billing :)