[Answering myself…]

Huh, I guess not.

You can still use harnesses/adapters that use ‘claude -p’ to connect behind the scenes. But the billing is extremely unclear, and it sounds like they use ‘more plan per token’ than just using Claude Code.

The Support page is very unclear, mentioning that you now get an allowance of tokens (and not mentioning the Pro plan at all in that section), and also saying that they’re backing off on plans they previously announced in June without saying what those those plans were, or what the status quo before them was:

https://support.claude.com/en/articles/15036540-use-the-clau...

…and there’s also this GitHub issue showing that tokens are ‘more expensive’ when using `-p`:

https://github.com/anthropics/claude-code/issues/97074

Yeah this was also my impression, which is why I asked.

Claude seems to think that the only possible path is piping through `claude -p` in the CLI, but Pi doesn't do that out of the box. There are extensions (e.g. opius) that do, and it's not clear if A\ will ban you for it.

https://claude.ai/share/a1e4f4be-ef6a-4db1-a656-bddcf30540d0

Zed GUI allows you to do it it's very straightforward, you click on new Claude thread, subscription, your browser opens, you allow the access and that's it.

https://zed.dev/docs/ai/external-agents

In Zed, Claude over ACP is still using the Claude Code harness but the rendering is done in the editor. It works really well.