7 ms·
> Also, Claude has made it apparent time and time again that it does not want people using Claude Code as a "tool" in a workflow. Why would Anthropic get to di
by gunapologist99 3mo ago
> Also, Claude has made it apparent time and time again that it does not want people using Claude Code as a "tool" in a workflow.
Why would Anthropic get to dictate how someone uses a "tool" (that's literally what Claude Code is... a tool in a workflow)
They're swimming upstream. Trying to maintain a rapidly shrinking moat and not being very creative about it. Making enemies of your users is often a failing strategy.
- BeetleB 3mo ago[flagged]
- dakolli 3mo ago[flagged]
- AnIrishDuck 3mo ago> Why would Anthropic get to dictate how someone uses a "tool" (that's literally what Claude Code is... a tool in a workflow) This is a direct conflict in framing. They clearly do not see Claude Code as a "tool in a workflow" but instead as a service that will eventually replace all programmers. I think the self-evident quality of the various parts of the Claude Code universe is a pretty obvious indicator of the problems with that approach. It is still important to understand a party's thinking if you want to understand their position. > They're swimming upstream. Trying to maintain a rapidly shrinking moat and not being very creative about it. Making enemies of your users is often a failing strategy. Time will tell, but I agree that they are indeed in a tough spot. Probably not for the reasons that they think.
- NewsaHackO 3mo agoI agree, my wording was a bit off. What I meant was a tool call in a harness. Claude Code should itself be the harness.