@heyhuynhgiabuu/pi-oauth-mistral
Pi extension: Mistral subscription sign-in via browser OAuth for the built-in mistral provider, targeted at Pi 1.5.0.
Package details
Install @heyhuynhgiabuu/pi-oauth-mistral from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@heyhuynhgiabuu/pi-oauth-mistral- Package
@heyhuynhgiabuu/pi-oauth-mistral- Version
1.1.0- Published
- Nov 7, 2026
- Downloads
- 532/mo · 73/wk
- Author
- killerkidbo
- License
- MIT
- Types
- extension
- Size
- 35.2 KB
- Dependencies
- 0 dependencies · 2 peers
Pi manifest JSON
{
"extensions": [
"./extensions/mistral-subscription"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
pi-oauth-mistral
Pi extension: Mistral subscription sign-in through browser OAuth for Pi's built-in mistral provider.
This is a maintained fork of 5omeOtherGuy/pi-mistral-subscription, pinned to Pi 1.5.0.
Why this fork exists
The upstream package is tested against Pi 1.4.0 and its shipped code has not changed since 2026-10-31, two days before Pi 1.5.0 was released. It does work on 1.5.0 (see Verification), but the owner wanted a copy they control, without waiting on upstream for a 1.5.0 baseline.
Fork base: v0.2.0-2-g8fb0d5c (v0.2.0 plus two docs/lockfile commits).
What differs from upstream
Small by design — the upstream logic was already correct.
- Pi 1.5.0 baseline.
peerDependenciesand dev dependencies are1.5.0instead of>=0.99.0/1.4.0. - Package rename.
@heyhuynhgiabuu/pi-oauth-mistral. The extension path and provider ids are unchanged, so/loginand/modelbehave exactly as before. /mistral-usagecommand. New in this fork: prints the Vibe Code and API allowances for the current period. See Checking the allowances from Pi.- Stale comments corrected. Upstream claimed Pi's catalog may lack
mistral-large-4,zai-glm-5-3andzai-glm-5-3-flashuntil an online catalog arrives. Verified in 1.5.0: all three ship in the built-in catalog, and themistralprovider has nofetchModelshook, so no online catalog fetch happens for it. - One test fixture replaced. Upstream asserted on
pixtral-large-latest, which no longer exists in the 1.5.0 catalog. The assertion now useslabs-leanstral-1-5-1, a model that is present and still hidden by the overlay.
What upstream got right, and this fork keeps
The overlay is smaller than it looks. Verified against the 1.5.0 catalog:
| Overlay entry | Still needed on 1.5.0? |
|---|---|
Hide labs-leanstral-1-5-1, mistral-large-4-0-8 |
Yes — both remain in the catalog |
| Hide the other 6 entries | No — already absent from the 1.5.0 catalog (kept for older hosts on the peer range) |
glm-5-2 / zai-glm-5-2 / deepseek-v4-1-flash-1017 reasoning levels |
No — 1.5.0 already declares identical maps |
deepseek-v4-1-flash-1017 image input |
Yes — 1.5.0 declares ["text"] |
mistral-large-4 output cap at 32,768 |
Yes, and this is the important one |
That last row is the real reason to run any version of this package. Pi 1.5.0 still declares a 262,144 output limit for mistral-large-4. Upstream reports one empty tool call burning 32,768 tokens, which would let a runaway turn cost eight times as much. Removing the package restores the 262k ceiling.
Install
Requires Pi 1.5.0 or newer and Node.js 22.19.0 or newer.
pi install git:github.com/heyhuynhgiabuu/pi-oauth-mistral
Then /login → Sign in with an account → Mistral, and pick a model with /model or --model:
pi --model mistral/zai-glm-5-3 --thinking max
The footer shows (sub) while the sign-in is active.
Billing: two separate pools, not one
Upstream's README says the plan "includes a monthly usage budget shared across Studio, the API and Vibe Code". That is wrong, at least on an Education plan. The Mistral Admin Panel shows two independent allowances:
| Allowance | Covers | Plan example |
|---|---|---|
| Included API usage | Studio / API keys | $15 / month |
| Included Vibe Code usage | Vibe Code, including this extension's sign-in | $150 / month |
Measured on an Education plan (Pro with student discount): a request through this extension's OAuth sign-in moved the Vibe Code allowance, not the API one. That is the whole economic argument for using this instead of a plain Studio API key — a coding agent exhausts the API pool quickly, while the Vibe Code pool is 10x larger.
Both pay-as-you-go toggles were off, so exhausting an allowance stops usage rather than producing a bill. Check your own Admin Panel before relying on any figure here.
Checking the allowances from Pi
/mistral-usage prints both pools for the current period, using the credential the sign-in already stored:
Mistral EDU plan. Vibe Code: $1.28 of $150.00 (0.9% used), resets 2026-12-01. API: $0.08 of $15.00 (0.5% used), resets 2026-12-01.
It calls GET https://api.mistral.ai/v1/billing/budget and /v1/billing/subscription with the sign-in key as a bearer token (checked 2026-11-06). Three details of that response are worth knowing if you query it yourself:
- The top-level fields repeat the API budget.
initial_budgetandusage_percentagesit at the top level as a copy ofapi_budget. Readvibe_budgetandapi_budgetinstead, or the Vibe figure silently becomes $15. usage_percentageis a percentage, not money. Convert it:initial_budget * usage_percentage / 100./v1/admin/*does not work with this key. Those endpoints (/v1/admin/usage,/v1/admin/spend-limit) return 401 with the sign-in credential; they need an admin-scoped key./v1/billing/*is the usable path and already carries both pools.
A failed lookup reports the reason and leaves the session alone. Both header styles work on api.mistral.ai; console.mistral.ai/api/... rejects the key either way (401), so billing reads only go through api.mistral.ai.
Security notes
- No runtime dependencies. Every
@earendil-works/*import isimport type, erased at load. Onlynode:utilandnode:cryptoare used. An install leavesnode_modulesempty. - No install scripts.
package.jsondeclares no lifecycle scripts. This matters becausepi installrunsnpm installwithout--ignore-scripts, andpi update --extensionsdoes agit reset --hardplus reinstall. - Two hosts, both Mistral.
console.mistral.aifor the sign-in only,api.mistral.aifor inference and the/mistral-usagebilling reads. PKCE is S256 with 64 random bytes;code_verifiergoes only toconsole.mistral.ai. Bothsign_in_urlandpoll_urlare validated against their expected origins before use. - The flow mirrors Mistral's own CLI. Verified against
mistralai/mistral-vibe→vibe/setup/auth/http_browser_sign_in_gateway.py: same/vibe/sign-inpath, same payload, same poll states, same/exchangecall. It is an internal endpoint of the Vibe CLI, not a published API contract.
Treat that last point as the standing risk: the endpoint can change without notice, and Mistral's consumer terms exclude "Mistral AI Studio and access to any of our APIs". Using the subscription through Vibe Code usage is the reading that fits what the plan sells; that is an argument, not a guarantee.
Verification
Run on Pi 1.5.0 with Node 26.13.0:
npm ci --ignore-scripts
npm run check # lint, tests, typecheck, secret scan, pack check
Typecheck passes with zero errors. Two upstream tests asserted on models that no longer exist in the 1.5.0 catalog; one was replaced, the other only asserts a model the overlay hides.
No test contacts Mistral or uses real credentials. The OAuth tests inject a fake fetch; streaming tests use a loopback HTTP server.
Migrating from upstream
The provider ids are unchanged, so a stored sign-in keeps working. To switch:
pi removethe upstream package (or remove it frompackagesin settings).pi install git:github.com/heyhuynhgiabuu/pi-oauth-mistral.- No
/loginneeded — themistralcredential inauth.jsonis reused.
Run /logout before removing the upstream package if you also intend to stop using this fork; without any extension, Pi cannot use a stored OAuth sign-in for mistral and leaves the provider unavailable.
Licence
MIT. Original work Copyright (c) 2026 5omeOtherGuy; modifications Copyright (c) 2026 huynhgiabuu.