271–280 of 568 posts
Earlier quoted context omitted.
The tweet is from 3 days ago and the bug report 4 days ago. Not sure if it was publicity that made it happen or not.
I know HN has a lot of devs, but I'm pretty sure none of us are going straight to Github to file for a refund from a bug. I'm assuming they notified customer service first and were rebuffed, then filed the bug.
"I need to let you know that we are unable to issue compensation for degraded service or technical errors that result in incorrect billing routing." Not sure I've ever seen a company openly take this position. This is a crazy policy.
> However, I need to let you know that we are unable to issue compensation for degraded service or *technical errors* that result in incorrect billing routing. This is very surprising. I've never seen a legitimate business not give refunds for technical errors of their own fault. Minimum Anthropic should credit the full amount to them.
The official response feels AI generated. I suspect this is a preview of our future. "You're totally right! I'm sorry but you're going to have to piss off anyway. Would you like to spend a few more hours discussing it with our AI chatbot? It won't help. But if it makes you feel better, it will probably cost us an extra $0.12 in tokens." I'll bet the first human at Anthropic learns about this from HN.
https://x.com/trq212/status/2048495545375990245 He is getting a refund along with an additional $200 credit from what I can see.
After going public and getting publicity. You shouldn't have to do that just to get a company to fix their own mistake. They stole $200, where do they get off saying they won't give it back?
Hey everyone, Thariq from the Claude Code team. We've been on this since the bug surfaced. Everyone affected is getting a full refund and an extra grant of usage credits equal to their monthly subscription as our apology. You can see my original post here: https://x.com/trq212/status/2048495545375990245 . We’re still working on sending emails to everyone affected. Our support flow wasn't set up to route a complex bug…
Would be more accurate. It still isn't setup. Talking to a bot as support who only tells you to talk to the bot for support is not actually support at all. It looks like support, but there's no way to ACTUALLY GET support.
Hey everyone, Thariq from the Claude Code team. We've been on this since the bug surfaced. Everyone affected is getting a full refund and an extra grant of usage credits equal to their monthly subscription as our apology. You can see my original post here: https://x.com/trq212/status/2048495545375990245 . We’re still working on sending emails to everyone affected. Our support flow wasn't set up to route a complex bug…
Hey everyone, Thariq from the Claude Code team. We've been on this since the bug surfaced. Everyone affected is getting a full refund and an extra grant of usage credits equal to their monthly subscription as our apology. You can see my original post here: https://x.com/trq212/status/2048495545375990245 . We’re still working on sending emails to everyone affected. Our support flow wasn't set up to route a complex bug…
For those of us not on X, what are the best communication channels for us to follow this sort of communication?
Hey everyone, Thariq from the Claude Code team. We've been on this since the bug surfaced. Everyone affected is getting a full refund and an extra grant of usage credits equal to their monthly subscription as our apology. You can see my original post here: https://x.com/trq212/status/2048495545375990245 . We’re still working on sending emails to everyone affected. Our support flow wasn't set up to route a complex bug…
> I need to let you know that we are unable to issue compensation for degraded service or technical errors that result in incorrect billing routing.
What prevents you from issuing compensations?
"I need to let you know that we are unable to issue compensation for degraded service or technical errors that result in incorrect billing routing." Not sure I've ever seen a company openly take this position. This is a crazy policy.