Yes, I have. And it's obvious that restriction was put there for a reason. The most obvious possible reason is that snatching OAuth made it possible for third party tools to utilize subscription to the fullest - like OpenClaw.

But these tools, including openclaw, didn't have to snatch the OAuth tokens, they could have used claude code built in headless stdio and consequences for Anthropic would be exactly the same. OAuth was just faster to plug in.

So if I open source my solution that allows opencode & openclaw to go through claude cli's headless mode, is this allowed? Is this a product that allows claude.ai login?

What if I open source a 1 line bash loop (e.g. ralph loop) that does the same?

What if I build a more complex bash loop that goes through my tasks in a text file, and calls claude cli for each?

I don't know at which point this becomes "offering claude.ai login" or a "product", or "building agents".

Here's my product:

while :; do cat PROMPT.md | claude ; done

Am I blacklisted now?

▲

szmarczak 2 hours ago | parent | next [-]

They just want people to pay more via API. Technically, your example would violate ToS, because the purpose matters. Like a license file may allow personal use and prohibit commercial use (unless you obtain a commercial license).

▲

NewsaHackO 3 hours ago | parent | prev [-]

Before I use time responding, I want to ask again: Did you actually read the website, especially the "Compare the Agent SDK to other Claude tools" section? It answers your question pretty thoroughly.

▲

gck1 2 hours ago | parent [-]

For the second time, yes. And it's still not clear at what point does a wrapper around claude cli running in headless mode become a 'product' that is going to get my account banned.

My guess is, and others have said this as well in the thread: "when you start utilizing your weekly quotas fully".

But obviously, they can't put "you can't use your weekly allocated quota fully". That would be way too honest and we can't accept that.

▲

NewsaHackO an hour ago | parent [-]

No, the link clearly says that if you are not using the harness provided by Claude for the Agent SDK (such as for making tool calls), you have to use the Client SDK. So attempting to prompt the Agent SDK with a third-party app so that the third-party app can then call a tool with the output is not allowed in the Agent SDK. You have to use the Client SDK (API).It even gives an example in the section I asked you to read, which is why I am seriously doubting whether or not you read it.

	▲	gck1 8 minutes ago \| parent [-]
		> the link clearly says that if you are not using the harness provided by Claude for the Agent SDK (such as for making tool calls), you have to use the Client SDK But you just made this up? There's no text on the page that says this. What the linked page does is explain technical differences between Agent SDK and Client SDK, and Agent SDK and cli (Agent SDK is just a wrapper around cli anyway). Neither tab says anything remotely like "if a third-party app prompts the Agent SDK and uses the output for tool calls, that's not allowed." You entirely fabricated this from the comparisons. And your assumption is wrong on another level. The Agent SDK specifically exists so that you can write your own harness and give it custom tools - that's its entire purpose. It's even documented in their custom tools guide [1]. So not only "using a third-party harness with the Agent SDK" isn't forbidden, it's the product's primary use case. There's no such thing as "harness provided by claude for the agent SDK" - you bring the harness. The only policy statement on that page is this: > Unless previously approved, Anthropic does not allow third party developers to offer claude.ai login or rate limits for their products.. But I've already addressed this, so it seems we're going in circles. [1] https://platform.claude.com/docs/en/agent-sdk/custom-tools