Re:Anthropic officially bans using subscription auth for thi...
by skeledrew on Thursday February 19, 2026 @01:13PM
(#47076980)
> OpenAI started nudging OpenClaw to burn even more tokens on Anthropic
Not possible: OpenClaw is run by a foundation, and is open source, which means OpenAI has no leverage to do such a thing.
Re:Anthropic officially bans using subscription auth for thi...
by ethbr1 on Thursday February 19, 2026 @04:11PM
(#47079453)
Because open source has always been completely independent of unrelated corporate entities who employ people to work on it?
Re:Anthropic officially bans using subscription auth for thi...
by skeledrew on Thursday February 19, 2026 @04:38PM
(#47079846)
Because anyone can actually check the code, which means if there's any funny business, someone will come across it eventually and blow it open.
Re:Anthropic officially bans using subscription auth for thi...
by notpushkin on Thursday February 19, 2026 @09:21PM
(#47082863)
There probably wouldn’t be anything funny-looking – it might look like a genuine mistake in implementation that burns 2× or 3× tokens somehow (which, considering OpenClaw is vibe coded in the purest sense of this term, would blend right in).
Re:Anthropic officially bans using subscription auth for thi...
by skeledrew on Friday February 20, 2026 @12:26AM
(#47084140)
Regardless, such things would eventually be found. Just as OpenClaw was tasked with finding and improving science repos (though unwelcome), it could - and very likely will - be tasked with improving its own codebase.
Re:Anthropic officially bans using subscription auth for thi...
by adjwilley on Saturday February 21, 2026 @01:02AM
(#47097906)
The bug that was causing the crazy token burn was added on Feb 15. It was claimed to have been fixed on Feb 19 (see https://github.com/openclaw/openclaw/pull/20597 ) but it's unclear to me whether that fix has been rolled out yet or if it completely solved the problem. (see https://github.com/openclaw/openclaw/issues/21785 )
TLDR: the commit broke caching so the entire conversation history was being treated as new input on each call instead of most of the conversation being cached.
This sounds like engineering, finance, and legal got together and decided they were in an untenable position if OpenAI started nudging OpenClaw to burn even more tokens on Anthropic (or just never optimize) + continually updated workarounds to using subscription auth. But I'm sure OpenAI would never do something like that...
At the end of the day, it's the same 'fixed price plan for variable use on a constrained resource' cellular problem: profitability becomes directly linked to actual average usage.