[stefan_]

Hermes is one of these OpenClaw clones, so this was certainly intentional, not a model hallucinating something.

I think the problem is clear. Anthropic saw their usage go up much more than their capacity could handle. There are a few tried and true solutions to this, like "increase the price" or "restrict signups so you can guarantee service to what you have already sold".

Then there is the "large scale fraud" option, where you materially change and degrade the service you have already sold. Just because you have obfuscated and mislead in how you describe the product you are selling doesn't mean you get to capture the cash flow of 1 year subscriptions then not honor that contract for the full duration.

[pbowyer]

> Hermes is one of these OpenClaw clones

So that's what it is. Reading its README I thought it was another harness like Pi [1], but with built-in memory so it remembers what it learns, and gets more capable the longer it runs.

Like Letta [2], Dirac [3][4] and the other "more experimental harnesses that look interesting but I haven't had time to try out".

1. https://pi.dev/

2. https://www.letta.com/

3. https://dirac.run/

4. https://news.ycombinator.com/item?id=47920787

[csoups14]

Late in replying to this, but just wanted to say I found this pretty compelling. I generally think people are too quick to assign to malice what could be assigned to incompetence. In this case I'm not convinced of that anymore especially given their public statements about these third-party harnesses. It does seem unavoidable that they'll have to move away from subscription-based pricing and towards token-based, but they're managing this in a really ham-fisted and user hostile way regardless.

[solenoid0937]

Mind pointing out where exactly in the contract you were allowed to use OpenClaw?

[jiggawatts]

Non-Claude client access is not permitted in the terms and conditions, except via API key.

The correct implementation of this condition by Anthropic on the server side would be to block usage by non-Claude apps via Claude's authentication mechanism, and allow it via the per-token API key billing.

Instead of a simple 403 error, which would block usage, they silently redirect to a different billing bucket, which is not ethical behaviour especially since it is based on fuzzy heuristics.

[InvidFlower]

Yeah, at the least it should alert the user that it is happening. Maybe the thinking was alerting it gives people signal on how to get around the restrictions, but having it silently charge from a different bucket isn't the answer either.

I think part of the issue is they were letting people use plan's API for random stuff, so people could do testing or small projects. Then the agents came along and exploded the cost, so they want to restrict those but still let some other usage, which I don't think is tenable.

I'm sure there is some way that they could enforce that all calls are coming from the Claude app or Claude Code. It might be hard to 100% enforce, with stuff running on a user's machine, but they could still could make it quite difficult, where someone has to be intentionally trying beat the system (like stealing encryption keys out of the Claude Code binary or something).