I got sick of the inconsistency caused by Anthropic tinkering with Claude Code and had canceled my 20x. My plan was to switch to Codex so I could use it in Pi. I am specifically talking about switching because of the harness, not model quality. Anyone else match my experience? I wonder how many other people recently did the same. It would be prudent of Anthropic to let people use Pro/Max OAuth tokens with other harne…
My experience is the opposite of this thread's consensus. Context: Full time SWE, working on large and messy codebase. Not working on crazy automations, working on fixing bugs, troubleshooting crashes, implementing features. Anthropic models write much better code, they are easy to follow, reasonable and very close to what I would done if I had the time... OpenAI's on the other hand generate extremely complex solutio…
Anthropic says OpenClaw-style Claude CLI usage is allowed again
271–280 of 318 posts
Re: Anthropic says OpenClaw-style Claude CLI usage is allowed again
#272Basically, as long as you are using an Anthropic library or tool, you can use your OAuth credentials. For example, you can use the Claude Agent SDK with your OAuth credentials. This is sweet because I can prototype all sorts of agents with Claude Code embedded inside, at a predictable monthly cost. One nice use case is turning skills into standalone tools or apps. You can also do convoluted things like run Claude Cod…
You don't really need to tmux at all for Claude Code CLI. Claude Code CLI supports streaming json input, and streaming json output; you can use stdin/out as a pipe to control Claude Code CLI. I'm doing this today in https://github.com/Cidan/ask -- works great.
Re: Anthropic says OpenClaw-style Claude CLI usage is allowed again
#273Peter here from OpenClaw. For context, here’s why our post reads the way it does: Boris from Claude Code said publicly on Twitter that CLI-style usage is allowed. We took that seriously and invested time building around that guidance. I even changed the defaults, so when using the cli we're automatially disabling features that use excessive tokens like the heartbeat feature. But in practice, Anthropic still blocks pa…
You can argue that this is unfair and they should provide clearer guidance. Well - as soon as they do people find ways to skirt the letter of the rules to once again take advantage of the economics of the subscription model. So should they just scrap the entire plan? Ruin it for people who are using it as it was intended (coding agent, light experimentation/headless use outside of that)? That doesn't seem right either.
Re: Anthropic says OpenClaw-style Claude CLI usage is allowed again
#274Peter here from OpenClaw. For context, here’s why our post reads the way it does: Boris from Claude Code said publicly on Twitter that CLI-style usage is allowed. We took that seriously and invested time building around that guidance. I even changed the defaults, so when using the cli we're automatially disabling features that use excessive tokens like the heartbeat feature. But in practice, Anthropic still blocks pa…
I mean surely you can understand the the difficulty of their position, right? It's as if Waymo offered a subsidized, subscription based plan that models a certain type of ridership as typical but then people start scheduling rides on a timer with no one in it, far outside the original use case of "Get me from point A to point B". And of course the line between what is acceptable is quite fuzzy. You could imagine it b…
There will be a time for OpenClaw, but in the current world with limited compute, that time is not now.
Re: Anthropic says OpenClaw-style Claude CLI usage is allowed again
#275Peter here from OpenClaw. For context, here’s why our post reads the way it does: Boris from Claude Code said publicly on Twitter that CLI-style usage is allowed. We took that seriously and invested time building around that guidance. I even changed the defaults, so when using the cli we're automatially disabling features that use excessive tokens like the heartbeat feature. But in practice, Anthropic still blocks pa…
Re: Anthropic says OpenClaw-style Claude CLI usage is allowed again
#276Peter here from OpenClaw. For context, here’s why our post reads the way it does: Boris from Claude Code said publicly on Twitter that CLI-style usage is allowed. We took that seriously and invested time building around that guidance. I even changed the defaults, so when using the cli we're automatially disabling features that use excessive tokens like the heartbeat feature. But in practice, Anthropic still blocks pa…
Peter, while we are on the subject of clarifying what is and isn't allowed I have a question: has OpenAI clearly communicated about precisely where one is supposed to be able to use their Codex quota? For instance, as far as I understand, it is allowed to use it with OpenClaw, but does it extend to any other coding harness? Say I have an app (potentially a paid one) and want my users to use their Codex quota in it, i…
Re: Anthropic says OpenClaw-style Claude CLI usage is allowed again
#277Peter here from OpenClaw. For context, here’s why our post reads the way it does: Boris from Claude Code said publicly on Twitter that CLI-style usage is allowed. We took that seriously and invested time building around that guidance. I even changed the defaults, so when using the cli we're automatially disabling features that use excessive tokens like the heartbeat feature. But in practice, Anthropic still blocks pa…
It seems with the new "--bare" flag they are introducing, a huge rug pull is coming as they plan to deprecate -p for unlimited users.
The docs now read:
> "Bare mode skips OAuth and keychain reads. Anthropic authentication must come from ANTHROPIC_API_KEY or an apiKeyHelper in the JSON passed to --settings. Bedrock, Vertex, and Foundry use their usual provider credentials. --bare is the recommended mode for scripted and SDK calls, and will become the default for -p in a future release."
Hope I am reading this wrong or this is clarified.
Re: Anthropic says OpenClaw-style Claude CLI usage is allowed again
#278Earlier quoted context omitted.
Peter, while we are on the subject of clarifying what is and isn't allowed I have a question: has OpenAI clearly communicated about precisely where one is supposed to be able to use their Codex quota? For instance, as far as I understand, it is allowed to use it with OpenClaw, but does it extend to any other coding harness? Say I have an app (potentially a paid one) and want my users to use their Codex quota in it, i…
I'm not sure they have "officially" said anything but they do allow Codex OAuth login for 3rd party coding agents: pi, opencode, etc. Employees on twitter have explicitly approved this.
Re: Anthropic says OpenClaw-style Claude CLI usage is allowed again
#279Earlier quoted context omitted.
> Keep in mind this is hearsay How, exactly, is that not saying something about the announcement?
It's saying something about the announcement, it's not saying something about the correctness of the announcement. I used the word hearsay to imply that flip-flopping should only be a judgement on the comms of the entity accused of flip-flopping, not information living on some third party source.
Of course, you're simply being pedantic. Everyone knows why they are making this change (which is more important than your silly take on what constitutes flip-flopping).
The point: Anthropic is losing subscribers because it has no idea what it actually wants to be.
Re: Anthropic says OpenClaw-style Claude CLI usage is allowed again
#280It'd be a lot cleaner if they just published explicit rate limits for each subscription tier instead of these vague policy statements.