There was another thread where some people pointed out, Amazon will give you access to Claude with better uptime for the same price (per million tokens up / down), downside is, it does not have the native ability to browse the web, but maybe that's a hidden blessing, since it's less likely to read some random website that has prompt injection embedded into it.

For coding its fine, I havent experimented too much with Amazon Bedrock myself, but I just might soon to check for any limitations.

From an economics perspective, it makes sense to make it more expensive if you're having trouble keeping up with demand for a service. It'll be tough getting used to because it was so nice and cheap

YMMV. I would still be very happy with Claude if it hard failed on 20% of tasks. You can always come back to it.

I say this as someone working for a tech company who does not have to foot the bill (in the >$1k per month bracket)

I also experienced and accept the 1990s levels of unreliability, which is my “internet generation”. My first access was lifting a handset and placing on a speaker/mic cradle.

Programmers these days are fucking spoiled. If it’s $220 worth of value for $200 - I get it. But I’m getting $100k of value for $10k and so I’ll put up with some shit.

We used to describe our startup as having 5 8’s of uptime

Not to mention substantially less open. I've been using an OpenAI subscription in Pi Agent for a couple weeks now and it's great. And from what I can tell, 5.5 is a heck of a model.

I'm either extremely lucky or Dario ran the direct fiber to my house because I have never had it go down in any meaningful way..

Is this just the API and I'm too much of luddite to actually use the API?

Interestingly, yeah, I can see that this would really cut into your subscription usage with the 5 hour rate limit windows...

I am an API user, and while it being down is super annoying, it isn't really as big of a hit to my overall usage as I can just prepare a bunch of stuff to run in parallel when it does come back up.

Don't say single nine, it sounds ugly and bad.

Say five eights of reliability. Maybe six.

Plus, they've dumbed down their models to the point where the value just isn't there like it was. If I have to go in and clean up after it, or constantly wrestle with it through prompts, what's the point? Just spending $200 a month to be frustrated at a machine.

It's lazy, does not take ownership and responsibility, wants to defer work, and I have to force it to check reality. It likes to guess and assume it's correct and I am wrong. Agents.md is not helping at all. It's in full enshittification phase, yay!

Single nine has good vibes bro. It means when the service is up the results are better. I read about it in a blog. The model hallucinates way less. Even less than grok

Plus one. I held off for too long out of concern that it wouldn't stack up and I'd come right back to Anthropic.

I switched a few days ago and work has been much less frustrating. Feels like CC did back in February before they started playing games.

It also doesn't eat nearly as many tokens, so it's saving me $100/mo.

I'm still not switching after Altman jumped on the cyberpunk totalitarian contract with the government

Lately I've been using claude mainly to design plans and do code reviews while Codex does all the implementation. Having two very different models helps to work out any weird quirks one might have.

I appreciate the objective anecdote, but obviously Coke™.

Honestly, I gotta agree, I find that I get way more frustrated with Claude recently than Codex.

I mean we just need technological advancements so we can get this hosted locally for people

more folks should be skeptical

GitHub is a long running business with a mature software stack running into scaling issues while they move to Azure and becoming Microsoft-ified. Claude is a new company in a new market with an extremely fast growing userbase running relatively novel AI infrastructure with a business model they are still figuring out.

I don't really blame Anthropic here.

I use openai team plan whenever its down because its down so much lol

Because you can't work without it?

Yikes.

I think if codex can fill in some functional gaps that shouldn’t be that huge - like having defined agents in plugins like Claude code - it’s actually a preferable product. It’s faster in every way, seems to manage context a lot better - compaction isn’t a completely end of world event to be avoided at all costs. With the addition of defined thinking and the fact it actually seems to follow tool calling instructions, it’s handler for permissions, and other features it’s frankly a better tool overall. 5.5 seems to be a reasonable model.

Anthropic seems to have really killed their advantage by squandering the immense good will they built up by blundering over and over again the last few months with the developer community.

Tonight, for instance, after the incident had recovered, I restarted my work. On my Max account my usage period completely exhausted in 4 minutes of sonnet subagent work. This was long after prime time, and the workload was a fraction what I normally do.

These days I run codex concurrently and have gotten my marketplaces and plugins and MCPs adapted to it - other than the agents which I do lean heavily on - and generally find it a capable replacement. Anthropic needs to take notice and get their house in order.

I found GPT 5.4 terrible. I just tested 5.5 and compared with opus its still not great.

I have max plans for both and over the past 5+ months now have built a custom "agent swarm" orchestrator with a database backed API and several skills CLI that the agents use to deliver orchestrated software factory runs.

We can use several different topologies (2 or 3 agents, etc.) but currently primarily use pair programming teams consisting of an opus4.7 for implementation and a codex5.5 for plan and code reviews, with a codex5.5 run-manager that pushes the agent lanes along and keeps things moving if they get stuck or escalate reviews to run-manager decisions.

Escalation to run-manager is a pretty regular thing as Codex5.5 generally picky and thorough and opus4.7 pushes back at times, and after three codex rejections we allow opus4.7 to escalate to run-manager decision to settle it. Usually, opus4.7 agrees and will continue iterating but it's not unusual that it will push back and escalate.

I've found codex5.5 is extremely capable. I just now finished a large multi-phase orchestrated swarm run with codex5.5 (xhigh) as the run-manager, presiding over 8 paired lanes, with 8 opus4.7 (high) implementers and 8 codex5.5 (high) reviewers, so 16 agents orchestrated and working in a swarm together. Codex5.5 managed that run perfectly for 14 hours with zero intervention needed by me.

Overall, I prefer to let opus4.7 draft the plans and then let codex5.5 offer git-diff style change feedback on plans, then let opus implement and codex review/manage. This seems to get the best result for me.

I get Claude to run Codex. You can do it that way, but not the other way around.

It also fits nicely. Claude plans better, and Codex has way higher limits.

codex works but code it spits out is still not as clean as opus.

When Claude is making "0 mistakes", all of his work is 100% done by Claude, therefore "coding is solved!" and we have more time to go on podcasts to tell everyone about it.

However, when there is an incident it is immediately "human error", not Claude.

> Can’t they prompt Mythos to give them better uptime?

Anthropic is currently "vibe coding" the situation right now.

Maybe they target certain types of infra rollouts for non-peak hours?

"But humans do it too as they just cool off and check out for the rest of the day."

It's fine for Claude to be unavailable when there is no work at these hours. However, the problem is Claude gave no notice.

At this rate, Claude being unavailable every day is no better than a human on a 9 - 5 working day job.

Almost like "Claude is only down because it's too busy" is cope and the reality is it's vibe coded trash.

98.68

Ouch.

switch to Pi.dev or any other multi model harness, you can switch between models every message if you feel like it.

Anthropic have blocked usage of your subscription however with third party harnesses.

You might search for a concept like `/handoff` that's in ampcode. I'm sure someone's built a skill for just this.

self hosted honcho (or other memory systems) and an api agnostic harness gets you most the way there.

you never rely on agent's own memory system. create memory system of your own

kilocode allows you to switch between models mid session!

Every day I am so much happier that I decided to go fully local for my needs.

4.6 has been excellent when used through the API. But I am right with you on 4.7, so I have been sticking to 4.6.

Introducing: Claude AWOL

I can't even sign in, however.

I've been a Codex devotee since around last August. I don't know why everyone is so bonkers about Claude Code. It's not the only belle at the ball. Codex is rock solid.

Here is one source that agrees: https://artificialanalysis.ai/models/capabilities/coding

Hurry! It'll be back up any minute now!

Oh no won’t someone please think about the trillion dollar corporation!