TRANSCRIÇÃOEnglish

Seriously, Anthropic??

34m 41s7,523 palavras1,033 segmentsEnglish

TRANSCRIÇÃO COMPLETA

0:00

I hate to do another video just dunking

0:01

on Anthropic, but they keep finding new

0:04

ways to just embarrass themselves in the

0:06

most public egregious fashions. We've

0:08

already seen them doing absurd things

0:10

like making sure your build more

0:11

depending on what system prompt you have

0:13

in clawed code because they didn't want

0:15

people using it with tools like OpenClaw

0:17

or other harnesses that they don't

0:19

support. On one hand, you can kind of

0:22

see why they would want that. I've been

0:23

running my Open Claw through a separate

0:24

service recently and just the pings it

0:27

does is about $5 a day of inference

0:29

through Opus 47. So I I get that. But on

0:33

the other hand, this is absurdity. The

0:36

fact that you're using your subscription

0:37

in one tool versus another should not

0:39

change whether or not they support it.

0:41

And even crazier, I shouldn't be build

0:43

money when I still have 100% of my usage

0:45

available because I used a tool you

0:47

don't like. But we can go further here

0:49

as Anthropic certainly has. They're no

0:51

longer just billing you based on what

0:53

tool you're using or what's in your

0:54

system prompt. They're now billing you

0:56

on what files are in your codebase. Even

0:59

that is not as bad as it is. They are

1:01

billing you on what file names are in

1:04

your git commits. This is a legitimate

1:06

report of a user who was paying for a

1:09

$200 a month sub for Claude Code that

1:11

was using Claude Code and ended up being

1:14

build $200 when they hadn't used any of

1:17

their usage in Claude Code because they

1:20

had a commit that had the term Hermes MD

1:23

inside of the commit message. I am just

1:25

as tired of talking about anthropic as

1:27

you guys are hearing me do it. But when

1:29

you [ __ ] up your code this genuinely,

1:32

hilariously and pathetically, I have to

1:35

make fun of you for it. And that's what

1:37

we're going to do now. The level of

1:39

incompetence at Anthropic right now,

1:42

powered by the disdain they have for

1:44

engineers as a whole, is at a level that

1:47

is hard to fathom. And as frustrated as

1:49

I am crashing out yet again about this,

1:52

I think this one perfectly summarizes

1:54

the problems I have. But if you want

1:56

somewhere better to spend your $200,

1:58

maybe somewhere that isn't going to

2:00

waste all of your time and money and

2:01

burn trust and destroy you, you might

2:04

want to check out today's sponsor. I

2:05

don't know about you all, but I'm

2:06

getting pretty tired of juggling all

2:08

these different subscriptions,

2:09

especially now that Anthropic banned us

2:10

from using my subscription with things

2:12

like OpenClaw. What if you want to use

2:14

OpenClaw and a VS Code plugin and a CLI

2:17

and all these other things that you

2:18

might use your inference for? Wouldn't

2:20

it be nice if there was one subscription

2:21

that covered all of that and good

2:23

integrations with all the tools you

2:24

already use to use it with? Today

2:26

sponsors Kilo Code and they've solved

2:27

all of this. Not only does their

2:29

subscription work for every different

2:30

thing you might want to do, they've also

2:32

built their own VS Code extension, Jet

2:33

Brains extension, CLI, and more. They

2:35

also have my favorite OpenClaw

2:37

integration by far. It's full and true

2:39

OpenClaw, but without having to spin

2:41

everything up yourself. You click the

2:42

get your assistant button and they'll

2:43

spin up the infrastructure and manage it

2:45

all for you. No Mac minis required. As

2:47

silly as this quote is, it's true.

2:48

They're the only solution that will

2:50

cover you from pull request to grocery

2:51

list, one subscription will cover

2:53

everything from the infrastructure to

2:55

the inference itself. Whether you just

2:56

want to write some code with the latest

2:57

model or try out OpenClaw directly,

2:59

there is no better place to start than

3:01

soyb.link/ilo.

3:02

Let's dive in. I think a little history

3:04

is important here before you can really

3:07

understand the level of egregiousness

3:09

that exists. That a not even existing

3:11

file, just an existing name of a file in

3:14

your commits is enough to cost you

3:16

hundreds of dollars. That's insane. We

3:19

need to talk about why Claude charges

3:21

for a markdown file that they don't

3:22

like. The Max 20x plan on Claude Code is

3:26

their highest tier. It is a $200 a month

3:28

plan. And this plan is incredibly

3:29

generous with the amount of usage you

3:31

can get. If you run it in a loop 247,

3:34

this $200 a month can get you over

3:37

$2,000

3:38

of inference. This number is citing the

3:41

API prices anthropic charges. If you are

3:44

going through their API, traditionally

3:46

they charge $5 per mill tokens in and

3:49

$25 per mill out on their flagship model

3:53

opus 47 as well as 45 and 46. The price

3:56

here, this $2,000 is if you look at the

3:59

tokens that you utilize as a subscriber,

4:02

run it in a loop for the entire month,

4:04

you will not hit limits until you've

4:06

reached about $2,000 of inference each

4:09

week. You're able to do around $500 of

4:11

work on the $200 plan. So, if you hit

4:13

the weekly limit they provide in Claude

4:15

Code, you did $500 of inference. I still

4:19

maintain my max 20x plan because I use

4:20

it for testing a bunch of different

4:22

[ __ ] I barely used it the last few

4:23

days. As you can see, you have a session

4:26

limit. A session is approximately 5

4:29

hours. It starts when you send a

4:30

message, which is already iffy because

4:32

if it was starting automatically on a

4:34

timer, then I could maybe send a message

4:36

or two before it resets and then get

4:39

more users. But I get why they also have

4:40

the weekly limits separately. They have

4:42

one for all models. They have a separate

4:44

sonnet only one because sonnet used to

4:46

be the thing we would use most in cloud

4:48

code. Now that opus is the default. This

4:50

separate sonnet only section makes

4:52

almost no sense at all. Your son uses

4:53

counts towards this limit as well as

4:55

your weekly and 5 hour session limits.

4:57

Like just unnecessarily confusing.

4:59

Speaking of which, Claude design is its

5:00

own separate thing. Absurd. Genuinely

5:03

absurd. But the point I'm trying to make

5:04

here is that if you have a weekly limit

5:06

and you hit the weekly limit, if you get

5:08

100% here, that is approximately $500

5:12

of usage. That's a lot of usage for

5:14

$200. And if you do that every week for

5:16

the month, you'll hit 2,000. That is a

5:19

10x discount. As such, they don't want

5:22

people to get that close to those

5:24

limits. So, if you have a tool that

5:26

automatically uses your inference,

5:28

they're not going to like that a whole

5:29

lot because now they're not going to get

5:32

the benefit of people like me who pay

5:33

and barely use it. I probably do $50 of

5:36

inference a month at most on this plan.

5:38

So, they're profiting off of me. But, if

5:40

I could use this with OpenClaw, I would

5:41

be using it more and then getting much

5:44

closer to the $200 I'm paying for. They

5:47

don't like that. They don't want that.

5:48

So, they're trying to restrict me from

5:50

being able to do that. There are some

5:52

legitimate arguments here and I will do

5:54

my best to steelman them. One of them is

5:56

caching. If you're not familiar with how

5:58

caching works in AI, I will do my best

6:00

to quickly summarize it. You have a

6:02

model that has a bunch of parameters.

6:03

Parameters are different chunks of text

6:06

that point to each other with different

6:08

levels of confidence. Like if you have

6:10

the capital of the United States is the

6:13

most likely thing to come after that is

6:15

Washington DC. Or if you just have

6:17

capital W Washington, it might point to

6:20

a couple different places. is it might

6:21

point to DC with high confidence. It

6:24

might point to state with slightly lower

6:26

confidence and it measures how likely

6:28

each of these things is and that's what

6:30

the model is. It's a bunch of these

6:31

tokens with arrows and vectors pointing

6:33

to and from each other to guess what the

6:35

most likely next thing is. When you hand

6:38

it a history of chat, it has to update

6:40

those pointers, those parameters based

6:42

on the history of the chat so far. If I

6:45

was to say, "What state do you live in?

6:47

Is it Washington?" The most likely next

6:50

thing is the question mark because

6:52

there's indication in the tone of the

6:53

other words I used that the most likely

DESBLOQUEAR MAIS

Registe-se gratuitamente para aceder a funcionalidades premium

VISUALIZADOR INTERATIVO

Assista ao vídeo com legendas sincronizadas, sobreposição ajustável e controlo total da reprodução.

REGISTE-SE GRATUITAMENTE PARA DESBLOQUEAR

RESUMO DE IA

Obtenha um resumo instantâneo gerado por IA do conteúdo do vídeo, pontos-chave e conclusões.

REGISTE-SE GRATUITAMENTE PARA DESBLOQUEAR

TRADUZIR

Traduza a transcrição para mais de 100 idiomas com um clique. Baixe em qualquer formato.

REGISTE-SE GRATUITAMENTE PARA DESBLOQUEAR

MAPA MENTAL

Visualize a transcrição como um mapa mental interativo. Entenda a estrutura rapidamente.

REGISTE-SE GRATUITAMENTE PARA DESBLOQUEAR

CONVERSAR COM A TRANSCRIÇÃO

Faça perguntas sobre o conteúdo do vídeo. Obtenha respostas com tecnologia de IA diretamente da transcrição.

REGISTE-SE GRATUITAMENTE PARA DESBLOQUEAR

APROVEITE MAIS DE SUAS TRANSCRIÇÕES

Inscreva-se gratuitamente e desbloqueie o visualizador interativo, resumos de IA, traduções, mapas mentais e muito mais. Não é necessário cartão de crédito.