alt Hacker NewsBut you understand that they changed the ToS today, and that's what I'm complaining about, right? "Read the ToS" isn't an answer to "I don't like this ToS change".
But you understand that they changed the ToS today, and that's what I'm complaining about, right? "Read the ToS" isn't an answer to "I don't like this ToS change".
I didn't see today's ToS change. But this was always against ToS. OpenClaw specifically is built against tech that breaks ToS.
Probably the ToS change was to make it more clear.
To be fair, the developer is the one breaking the ToS in the most significant way, breaking boilerplate reverse engineering clauses.
But the user also is very aware that they are doing something funny, in order to authenticate, the user is asked to authorize Claude Code, n ot Opencode or OpenClaw, it's clearly a hack and there is no authorization from Anthropic to OpenClaw, and you are not giving Anthropic authorization to give access to OC, the user asks Anthropic to give access to Claude Code, the only reason this works is because OC is pretending to be Claude Code.
The bottom line issue is that as a user you are paying for a subscription to a package that includes an expected usage. That package is not metered, but it is given on the condition that you will use it as it is expected to be used, by chatting manually with the chatbot, which results in a reasonable expected token usage. By using a program that programatically calls the chat interface, the token consumption increases beyond what was part of the original deal, and so the price should be different.
A similar scenario would be if you go to an all you can eat buffet, you pay for a single person, but then you actually unload an army of little clones that start eating the whole buffet. Technically it was an all you can eat buffet and you paid the price right? Well no, come on, don't play dumb.