| ▲ | NewsaHackO 2 hours ago | ||||||||||||||||||||||
Have you read the website? https://platform.claude.com/docs/en/agent-sdk/overview >Unless previously approved, Anthropic does not allow third party developers to offer claude.ai login or rate limits for their products, including agents built on the Claude Agent SDK. Please use the API key authentication methods described in this document instead. Seems clear-cut to me. | |||||||||||||||||||||||
| ▲ | gck1 an hour ago | parent [-] | ||||||||||||||||||||||
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? | |||||||||||||||||||||||
| |||||||||||||||||||||||