Codex pricing to align with API token usage, instead of per-message
121–130 of 212 posts
Re: Codex pricing to align with API token usage, instead of per-message
#122Re: Codex pricing to align with API token usage, instead of per-message
#123Earlier quoted context omitted.
Absolutely not. I took on some thins that would normally take 5-10 people and many months. Some people are turn out slop. I was really excited to try and make some impressive shit. My whole life has been dedicated to trying to embody what Apple preached in the early days. I knew this was coming, but I thought I had a little more time to try and get them over the finish line, ya know? Maintenance by hand might be achi…
> I took on some thins that would normally take 5-10 people and many months. Based on what, exactly? It's very easy to claim some software would've taken you months to make, but this is ridiculous. Estimating project duration is well known to be impossible in this field. A few years ago you'd get laughed out the room for making such predictions. > I’ve only got so much savings left to live on. Respectfully, what are…
I’m not ready to unveil the thing I alluded to, it’s important to me that it’s good and polished. But I’ve done quite well so far developing in Swift, Rust, Go, and coming up with marketing and design — things I definitely couldn’t do by hand without a lot more time and effort.
https://poolometer.com/ Is one of the things I’m almost ready to call ready. So much domain expertise or tedious math involved — I simply wouldn’t have bothered on my own, pre-AI
I agree it’s a huge existential risk that everyone is also amazing. So far that’s not true. I get hung up on a lot of little quirks, like getting Dolby Vision to play properly on Apple Silicon without Vulcan. Something I accomplished after about 2 weeks of relentless determination.
To be clear I’m just trying to answer your questions honestly. I understand the situation. It’s almost to my benefit the harder it is for non Software Engineers. But in our current reality, when I’m not launched yet, it’s more stress
Re: Codex pricing to align with API token usage, instead of per-message
#124Earlier quoted context omitted.
Is writing it by hand the old-fashioned way not on the table?
It's really not. As a one-person IT department I'm now able to build things in hours or days that it previously would have taken my weeks or even months to build (and thus they didn't get done). Things people have wanted for years that I didn't ever have the time for, I can now say "yes" to.
Dangerous too of course. So many times I’ve had subtle unexpected side effects. But it’s all about pinning thins down well and that’s what we’re all still figuring out well
Re: Codex pricing to align with API token usage, instead of per-message
#125Earlier quoted context omitted.
It's really not. As a one-person IT department I'm now able to build things in hours or days that it previously would have taken my weeks or even months to build (and thus they didn't get done). Things people have wanted for years that I didn't ever have the time for, I can now say "yes" to.
Then I would say they judged the situation correctly when they decided to raise prices. That said: competition will soon kick in.
I had my hopes up to switch to local but my first few passes didn’t pan out with that so far. But I’m optimistic it’ll land soon.
I think I need to lower my ambitions too. I got my hopes up since AI can do everything but how long it takes to do it right can really drag on
Re: Codex pricing to align with API token usage, instead of per-message
#126this is indicative to me that the exponential is slowing down. tool and model progress was huge in 2025 but has been pretty stale this year. the usage changes from anthropic, gemini, and openai indicate it's just a scale of economy issue now so unless there's a major breakthrough they're just going to settle down as vendors of their own particular similar flavor of apis.
I think it signals that they’ve been so successful that they need to ensure there is some direct financial back pressure on heavy users to ensure that their heavy token use is actually economically productive. That’s not a bad thing. Giving away stuff for free - or even apparently for free - encourages a poor distribution of value.
Jesus, the spin on this message is making me dizzy.
They finally try to stop running at a loss, and you see that as "they've been so successful"?
Here's how I see it: they all ran out of money trying to build a moat, and now realise that they are commodity sellers. What sort of profit do you think they need to make per token at current usage (which is served at below cost)?
How are they going to get there when less-highly-capitalised providers are already getting popular?
Re: Codex pricing to align with API token usage, instead of per-message
#127Earlier quoted context omitted.
Already paying for Google photo storage, AI pro for an extra $7 is a steal with anti-gravity.
I bought one of the google AI packages that came with a pile of drive storage and Gemini access. Unfortunately gemini as a coding agent is a steaming useless pile. They have no right selling it, cheap open weight Chinese models are better at this point. It's not stupid it just is incompetent at tool use and makes bad mistakes. It constantly gets itself into weird dysfunctional loops when doing basic things like editi…
Re: Codex pricing to align with API token usage, instead of per-message
#128Earlier quoted context omitted.
It’s kind of a rug pull to effectively raise the price like 10x. I can’t afford to finish some of my projects with this change
I don't think you can call it a rug pull when everybody saw it coming from miles away
Then I realized I was an idiot and this was magic.
But it now seems more like an introductory offer to use the API, as opposed to an alternative product / way to use their API product.
I thought it would get increasingly expensive, like say the $200 plan becomes $400.
Switching these plans to API metering doesn’t feel like it’s a separate product anymore?
Re: Codex pricing to align with API token usage, instead of per-message
#129Earlier quoted context omitted.
We are exiting a hype cycle, well into the adoption curve. Subscriptions were never going to last. My next step is going to be evaluating open and local models to see if they are sufficiently close to par with frontier models. My hope is that the end of seat based pricing comes with this tech cycle. I was looking for document signing provider that doesn't charge a monthly, I only need a few docs a year.
I'm developing software in this area right now, so I try a lot of the new models. They're not even close for coding tasks. It basically comes down to 26b parameters vs 1T parameters / quantisation / smaller context sizs, there's no comparison. However, for agentic work, tool calling, text summarisation, local LLMs can be quite capable. Workloads that run as background tasks where you're not concerned about TTFB, cold…
you can tell gemma4 comes from gemini-3
Re: Codex pricing to align with API token usage, instead of per-message
#130Earlier quoted context omitted.
I bought one of the google AI packages that came with a pile of drive storage and Gemini access. Unfortunately gemini as a coding agent is a steaming useless pile. They have no right selling it, cheap open weight Chinese models are better at this point. It's not stupid it just is incompetent at tool use and makes bad mistakes. It constantly gets itself into weird dysfunctional loops when doing basic things like editi…
Are you using gemini CLI or antigravity? The former is not really comparable to the latter in terms of quality. I wouldn't say antigravity is as good as the competition but it's pretty close. Miles behind is overstating it.
Antigravity wants me to switch IDEs, and I'm not going to do that.