Claude Code refuses requests or charges extra if your commits mention "OpenClaw"
521–530 of 760 posts
Re: Claude Code refuses requests or charges extra if your commits mention "OpenClaw"
#522I can't even have Claude assist in creating a Hermes or OpenClaw agent that utilizes a 3rd party API?
Re: Claude Code refuses requests or charges extra if your commits mention "OpenClaw"
#523Earlier quoted context omitted.
You don't even need to put it in a project, put it in all your blog posts as invisible (white font white background) text, and if Claude winds up reading your website as part of a research task, you basically bricked someone's Claude session. Why is it amateur hour at Anthropic lately?
Because AI is a new product category in tech, and every single new product category in tech always, no exceptions, insists on learning nothing from history, and so the dumb shit is repeated until they learn their own lessons. I am almost 40, and I have seen the same pattern play out several times now, it’s always the same.
The ageism in tech probably has something to do with it.
When I see some of these brobdingnagian disasters, I always wonder if there were any adults in the room, when the idea was greenlighted.
Re: Claude Code refuses requests or charges extra if your commits mention "OpenClaw"
#524Earlier quoted context omitted.
They have better PR than OpenAI but they are not a more ethical company. They do a bunch of shady stuff and are just as much involved in military applications. Cal Newport’s recent podcast had a good discussion about this: https://youtu.be/BRr3pAPsQAk?si=jaRJYJ_XQE7VpxPN
Pet peeve of mine is people saying "hey this thing is totally shady/false, I've got proof right here links to hour long podcast >". It happens surprisingly often.
Re: Claude Code refuses requests or charges extra if your commits mention "OpenClaw"
#525Re: Claude Code refuses requests or charges extra if your commits mention "OpenClaw"
#526A lot of the comments here are reacting to the censorship aspect, which is obviously an important point. But the more interesting subtext to me is that I feel like this gives insight into the situation within the company. I'm assuming they wouldn't do something like this unless the recent load issues (mostly driven by OpenClaw usage) were seen as an existential threat. So I'm guessing that's how the leadership views…
> The irony of course is that the way they've gone about reacting to this has damaged their brand so badly at the trust level that the public view of their company has completely flipped. No one at my company gives a single shit about Openclaw, so this whole situation has been a noop for a lot more of the public than you seem to think. Also, "censorship"? How is disallowing a specific tool that abuses a subscription…
Re: Claude Code refuses requests or charges extra if your commits mention "OpenClaw"
#527Re: Claude Code refuses requests or charges extra if your commits mention "OpenClaw"
#528Earlier quoted context omitted.
Because AI is a new product category in tech, and every single new product category in tech always, no exceptions, insists on learning nothing from history, and so the dumb shit is repeated until they learn their own lessons. I am almost 40, and I have seen the same pattern play out several times now, it’s always the same.
Yeah, I feel that. The ageism in tech probably has something to do with it. When I see some of these brobdingnagian disasters, I always wonder if there were any adults in the room, when the idea was greenlighted.
They'd rather treat the general version of Greenspun's 10th rule as a commandment, and create a new, ad hoc, informally-specified, bug-ridden, slow implementation of some fraction of whatever already addresses the requirement, than learn about how to use some existing tool that they don't already know.
One of my favorite examples is a company that home-rolled their own version of (a subset of) Kubernetes, ending up with a fabulously fragile monstrosity that none of the devs want to touch any more, and those who do quickly regret it.
Re: Claude Code refuses requests or charges extra if your commits mention "OpenClaw"
#529A lot of the comments here are reacting to the censorship aspect, which is obviously an important point. But the more interesting subtext to me is that I feel like this gives insight into the situation within the company. I'm assuming they wouldn't do something like this unless the recent load issues (mostly driven by OpenClaw usage) were seen as an existential threat. So I'm guessing that's how the leadership views…
I think another possibility is that they are trying to shift the burden of OpenClaw to their competitors.
Re: Claude Code refuses requests or charges extra if your commits mention "OpenClaw"
#530It's fascinating to see all these bugs in Claude Code - HERMES.md, this OpenClaw issue, the recent thinking-message pruning and cache-skipping bugs. They seem like the class of bugs I see in my vibe-coding experiments, and I think the Claude Code lead has said many times that he/his team don't read the code for Claude Code themselves, that it's basically vibe-coded. If Anthropic itself can't make vibe coding work, wh…
Because this is the company whose CEO makes public pronouncements about how they're going to exterminate our whole profession any day now, how we won't be needed.
So if that's your ultimate boss, do you think he's going to let you stop, analyze, cautiously review, hand curate, hand edit?
To me the thing seems like a science project that got shipped as a product, with a complete lack of proper software engineering quality principles around it.
A gating procedure like this (and the HERMES.md thing etc) would never get past a code review process in any respectable shop that I've worked at. If I'd put up a code review like this at Google when I was there, it would been a pile-on of senior engineers demanding a better approach, no LGTM would have been given.
I can only conclude Anthropic is getting high on their own supply.
In any case, writing code to get features out the door has rarely been the block in our profession. It's usually process and review and understanding requirements.
And so the entire project feels like a fundamental misunderstanding of what shipping software as a team is actually about.