Earlier quoted context omitted.
So OpenAI the company making the AI and using it inhouse is ripe for disruption? What?
I want some of what he’s having please
[dead]
Codex on AWS bedrock bug causing 10x charges
51–60 of 79 posts
Re: Codex on AWS bedrock bug causing 10x charges
#52Funny 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.
I doubt anyone announces when they have under billed. OpenAI has also done many low price deals and quota resets.
Usually it's user's incentive to control over-billing and company's one to make sure there's no under-billing :)
Re: Codex on AWS bedrock bug causing 10x charges
#53Our 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"
"causing" -> "costing", right?
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.
Re: Codex on AWS bedrock bug causing 10x charges
#54Earlier quoted context omitted.
It’s really cool that we have this proof that US companies are half year behind Chinese models in architecture.
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
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.
Re: Codex on AWS bedrock bug causing 10x charges
#55[flagged]
Re: Codex on AWS bedrock bug causing 10x charges
#56Earlier quoted context omitted.
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
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.
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?
Re: Codex on AWS bedrock bug causing 10x charges
#57The 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.
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
Re: Codex on AWS bedrock bug causing 10x charges
#58But but according to Mr Altman, we've like entered the singularity. Right? Who cares about a billing issue?
Re: Codex on AWS bedrock bug causing 10x charges
#59Wow, 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 breakpoi…
> 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.
Re: Codex on AWS bedrock bug causing 10x charges
#60Earlier quoted context omitted.
It’s really cool that we have this proof that US companies are half year behind Chinese models in architecture.
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
There is so much misinformation in the ecosystem, parrots just hitting "Reply" without thinking one iota, you really cannot trust "human" opinions on the internet anymore, anywhere.
Same with local LLMs, I'd love to use them for my day-to-day software engineering, and I'm not exactly GPU poor, then people with 12GB VRAM try to convince me their local setup is perfectly fine running latest Qwen and it does real engineering but whenever I try, they're a far cry from what Codex+GPT 5.x would do.
Only way to be sure is creating your own private benchmarks and use those, and the difference in quality becomes very apparent, very quickly, for your specific use cases.