upvote
Have you actually used their products? They are janky, full of bugs and barely work half the time.

They write 100% of their code with Claude. Some of their engineers apparently burn over 100k worth of tokens per month.

It’s not surprising they ship fast at all when the product is actually falling apart at the seams and they just vibe code everything.

reply
The Claude Code TUI app is pretty solid. I use it heavily and I get great results from it. But with the mobile app, Claude Code remote is basically unusable (weird disconnect bugs) and Claude Code cloud has issues as well (UI hides approval confirmations; must reconnect to see them). So yeah, I imagine what you're saying is true. There are at least some major gaps in their QA process. It's ironically a pretty convincing case to keep humans in the loop. It's honestly shocking to me that those features were actually shipped in their current state. You run into the problems immediately.
reply
I have a very different experience. Claude code tui is the worst tui I have ever used. How is it possible that an inactive tui regularly eats 8gb of ram, has freezing issues and rendering issues?

If I wasn’t forced to use it I wouldn’t as there are better options available.

reply
I agree with you about the Claude Code TUI. I switched to it weeks after it was released. The browser interface is great for quick chats and talking through ideas/concepts, but not for coding. What I love about the TUI is that it can see all your repos as once so it has the full picture all the time. You can't get that with the web version.
reply
I don't find criticism like this particularly compelling. Most products (written by humans) have the same failings. The few that aren't are exceptions to the rule or develop very very slowly and carefully.
reply
I think to the extent they are making a speed v quality tradeoff, I think they are making the right call. 10x speed over quality any day for me. Reminds me of:

"If brute force doesn't work, you aren't using enough of it." - Isaac Arthur

reply
Everyone is making this tradeoff now. Surely nothing bad could come from it.

In the meantime I can’t even continue a Claude Code session I started on desktop on my phone. What’s the point of shipping a billion features of they are all half baked?

reply
Everyone is NOT making that tradeoff. Maybe we will be forced into it someday, but my team is leveraging AI to increase the quality of code far beyond what we would have done without it. Some of us are using it to engineer better solutions.

Example: we are putting a lot of energy into removing technical debt, reorganizing the code to remove unneeded abstraction and complexity, and creating missing tests and automation. We're not just burping out new untested and poorly reviewed functionality.

reply
It’s a phase, for sure things will turn around in the future once the hype of “oh we can now ship fast” is gone.

fwiw I’ve had this open source browser ui that sits on top of your claude code, gemini and codex and picks up/starts your sessions from any device https://github.com/siteboon/claudecodeui

reply
the point is VC money
reply
They also pay... insane salaries, like double industry average. That coupled with an IPO on the horizon means they probably have their pick of engineers.
reply
Their interviews are actually very much focused on how fast you can code something that works.
reply
You have 23 year olds earning $2mn/year, at least it isn't in HFT though!
reply
They clearly vibe code a lot (most? all?) of their stuff, and it shows. Elementary features are broken regularly and while I appreciate them trying new features, I'd appreciate it more if existing ones were reliable and promptly fixed if broken.
reply
Trouble is, vibe coding refinements and bug fixes works well but probably isn't a good track to promotions at Anthropic (or virtually any other company.)
reply
Meanwhile, you still can't Sign in with Apple on the website.

But you can Sign in with Google.

If you signed up with your Apple on the iOS Claude app, to access your account on the computer, you have to open the passwords app and copy your random email address and paste it into the Claude website login.

Also if you try to copy-paste a prompt from Notes etc into the Claude chat, it gets added as an attachment, so you can't edit the prompt. If you do the four-finger shortcut to paste it as text, it mangles newlines etc.

Why are they so dumb about such basic UX for so long?

reply
> you still can't Sign in with Apple on the website.

Apple forces developers to offer Sign in with Apple on iOS devices if any other sign in service is used. Apple can't force them to do it on non-Apple platforms.

reply
> If you signed up with your Apple on the iOS Claude app, to access your account on the computer, you have to open the passwords app and copy your random email address and paste it into the Claude website login.

Isn't this basically Apple's fault? When you signed up, Apple provided a fake email address in leu of your real one. This is great for privacy but means the service has the wrong email.

I'm sure they didn't want to provide an Apple sign in option at all, but it's required by App Store rules.

reply
They could also just implement sign in with apple on their website, they have the ability to sign in with google so not supporting Apple is still a weird choice they are making.

Apple should not have had to require developers to have options other than Google for authentication, but clearly some companies have to be dragged kicking and screaming.

So clearly they support it, and there is no reason it should not work on the web also.

reply
A vendor doesn't have to bend for another.

Always best to sign in with your own email address.

reply
There are a lot of websites that only support third party login, so that is not always an option.

They don't have to bend for another, but they made a choice to put an app on iOS. They added support for apple signin, and then for some reason did not put it on their website.

You can criticize Apple for requiring that all you want, but they clearly have support for it and are choosing to not put it on their website which is causing a worse user experience.

IF apple did not support website loggin than sure, but they do. So the ability to fix this is on Anthropic (and many other websites).

If you are already going to support third party login you should not limit it to only Google accounts and there is no reason to support Apple on iOS and not the web.

Also for the record, Apple only requires sign in with apple if you already support third party authentication. So if you are already going to support that, giving the user more choice (and making it so we are all a bit less dependent on google) is a good thing.

reply
No criticism from me towards apple or Anthropic. Both parties made their choice. Apple was late to the identity business and the other ships had already sailed.

Third party logins are an extension and a massive risk to any website that doesn't include email hosting.

We have see identity providers dissapear, and people may change their mind.

Easiest way is to register you rown domain and use it with an identity provider of your choice and be able to move it anywhere.

Otherwise we are a faceless citizen of a corporation that can handle access to our identity and everything attached to it without recourse or access to anyone.

reply
Bruh.

Are you seriously trying to justify offering Sign in with Google but not ALSO offer Sign in with Apple because of some contorted principle, the method which HELPS users maintain their privacy? What the actual f.

Antrhopic's UX is just trash, the worst of all the major AI products.

They have this "I'm special" syndrome where they think they can get away with doing shit weirdly and not offer basic features that everyone else does, and the reason why I never purchased any of their services again after the first month, and had to replace my payment info with a throwaway card because they wouldn't let me remove it, again unlike everyone else.

reply
I don't think it's hard to understand why a service would want to support Google as an identity provider but not Apple. Google is probably the most commonly used provider out there, at least outside of the enterprise space.
reply
> Always best to sign in with your own email address.

Oh boy

Saying this in 2026 is just.. oh man. just wow

reply
> Always best to sign in with your own email address.

Using a randomly generated email per service is a huge improvement over always using the same email.

reply
Not really. It's the user's fault. Apple provides an option to hide your email, it's not required. It's an option that shows up when you're prompted to create an account.
reply
Oh, I agree with this.

My original thinking was that Apple makes it too easy for a general audience to hide their email without considering the implications (the service won't know your email). But of course there's a tension here, since you also want the option to be easy and accessible.

The party I do not consider at fault in this case is Anthropic.

reply
> I'm sure they didn't want to provide an Apple sign in option at all

But they wanted to provide a Google Sign In? wth?

> This is great for privacy but means the service has the wrong email.

So harm the users to benefit the service? wtf?

I don't want to give my real email or anything to random services, specially not one like Claude where they don't even let you remove your payment info.

reply
> I don't want to give my real email or anything to random services, specially not one like Claude where they don't even let you remove your payment info.

The original complaint was:

>> If you signed up with your Apple on the iOS Claude app, to access your account on the computer, you have to open the passwords app and copy your random email address and paste it into the Claude website login.

Either you use your original email or you use a per-service email. Apple helps you do the latter, but this does come with UX tradeoffs.

Using a per-service email, then complaining that the service does not have your real email, strikes me as misguided.

reply
> but this does come with UX tradeoffs.

Only when a dumb service refuses to support Sign In with one pro-privacy provider but does for another anti-privacy one.

reply
Add to the list backtick handling. If you start a backtick block on the claude web chat, you cannot leave it with the keyboard. You are now stuck between the backticks. It is as if they wanted to reproduce Slack misery.
reply
Pressing the down arrow while inside a block exits it for me.
reply