> Ability to use the plan outside of the official harness. Codex wins. Anthropic does shit like bills requests as extra usage if it sees a hermes.md in a commit.
I'm quite puzzled about why Anthropic is so hellbent on blocking other coding agents. It's not like Claude Code has any secret sauce, right? And doesn't Anthropic make monkey off API usage, and their magic is on the model side anyway?
Originally it was because Anthropic was so compute constrained they relied on the extra care the Claude harness took with caching (heavy use of cache breakpoints etc) that other harnesses didn't.
I think that is less of a factor now, and I think Anthropic have backed off some on being as strict (eg, AFAIK they never implemented the two-tier "claude -p" pricing model they were planning)
It's for lock-in - same reason why it took them so long to finally support AGENTS.md.
But to be fair, they don't really enforce the harness rule that much anymore. I guess if your harness doesn't do a lot of weird things like a lot of cache misses, or triggers some distillation attacks, or some broader Chinese fingerprints, they're tongue-in-cheek okay with you using a third party harness.
You can use Claude’s subscription in Pi now? Last I tried it opted for extra usage.
Not natively, as it's still a ToS violation and adding that in pi would go against pi principles, but there are many plugins/proxies that make it work.
oh-my-pi supports it natively (again, still a ToS violation), by impersonating claude code's fingerprints.
I have been using oh-my-pi with 3 claude subs for the past few months without any issues. Even native server-side OAI/ANT compaction works out of the box.
They want to lock people into using the Claude Code ecosystem to make switching to other providers more difficult.