pi-claude-pro

Use your Claude Pro or Max subscription in Pi, with your usage in the footer and a clear message when a limit is spent.

What it does

When the Anthropic model uses a subscription token, the extension:

• sends the request with the Claude Code identity: user agent, x-app header, session header and billing block;
• moves Pi's documentation section from the system prompt to the start of the first user message;
• uses the full context window from Pi's model catalog;
• shows your 5-hour and weekly usage in the footer;
• replaces the error of a spent limit with a clear message and its reset time, and stops pointless retries.

Requests that use an Anthropic API key are not changed.

Compatibility with other extensions

The adapter accepts structured Pi prompts and complete text prompts returned by other extensions. It does not require a specific extension configuration.

Only complete <docs> blocks starting with Pi documentation are moved. Custom documentation, instructions, tools and skills remain unchanged. Unrecognized or fragmented documentation stays in place.

Requirements

• Pi 1.x. The tests run against Pi 1.0.3.
• A Claude Pro or Max subscription.

Claude Code is optional. When claude is on the PATH, the extension sends its version. Otherwise it sends the bundled version, 2.1.289.

Install

pi install npm:pi-claude-pro

To try it for one session without installing:

pi -e npm:pi-claude-pro

To update or remove it:

pi update --extensions
pi remove npm:pi-claude-pro

Use only one extension that handles the anthropic provider. Remove other Claude subscription extensions before you install this one.

Set up

1. Start Pi.
2. Run /login, then select Anthropic (Claude Pro/Max).
3. Select an Anthropic model with /model.

The footer shows Claude Pro when the extension is active.

Footer

Troubleshooting

pi-claude-pro cannot run claude --version: Claude Code is installed but broken. Repair it, or remove it from the PATH.

Claude 5-hour limit reached: wait for the reset time, or enable extra usage in your Claude account.

usage lookup failed: Anthropic returned HTTP 429, and the usage endpoint did not answer. Pi retries the request.

No Claude Pro in the footer: run /login again and select Anthropic (Claude Pro/Max), not the API key. Then run pi list and check that no other extension handles Claude.

Risks and limits

• Unofficial. Anthropic does not support this package. Using a subscription outside Claude Code can break the Anthropic Consumer Terms. You accept this risk.
• Server contract. The request is valid only while Anthropic accepts the Claude Code identity that this package sends: headers, billing block and its checksum. Anthropic does not publish this contract and can change it at any time. The offline tests cannot detect such a change. Run npm run check:live to test the current contract.
• Pi versions. The peerDependencies range is *, because Pi requires it for the packages that it provides. The tests cover the Pi version in devDependencies.

Development

npm install
npm run check
pi -e .

The tests run offline. They load the extension in Pi, with Pi retries on, and replace the network with a fake Anthropic server.

The fake server accepts every request, so the offline tests do not prove that Anthropic accepts them. To check that, log in to Pi with your subscription, then run:

npm run check:live

It sends one small request to claude-haiku-4-5 and fails when Anthropic does not bill it to the subscription.

Report bugs on GitHub Issues.

Contributing and releases

1. Open a pull request. CI runs npm run check on Node 22 and 24.
2. Add user-visible changes under ## Unreleased in CHANGELOG.md.
3. To release, run npm run release -- <patch|minor|major|x.y.z> from an up-to-date, clean main. The script names the Unreleased section after the version, updates package.json, runs the checks, and opens a release pull request.
4. Merge the release pull request. The Release workflow publishes the package to npm with provenance and creates the GitHub release from the CHANGELOG section.

The workflow publishes through npm trusted publishing, so the repository stores no npm token. Before the first release, configure the package's npm trusted publisher for this repository, release.yml, and the GitHub environment npm.

License

MIT