pi-free-provider

Free models in pi, kept in sync automatically.

This extension gives pi two free pools as normal providers, with a model list that refreshes itself on every session start instead of going stale in a config file:

• clinefree — the free bucket on api.cline.bot (Cline's model router).
• zenfree / zenfree.res — the free tier of OpenCode Zen.

You bring your own credential (or use the device-flow login); nothing is shared and no quota is proxied through anyone else.

/model clinefree/reflection/beam-free
/model zenfree/deepseek-v4.1-flash-free

Requirements

Install

pi install npm:pi-free-provider

Other ways in:

pi install git:github.com/kslamph/pi-free-provider   # straight from git
pi install /path/to/pi-free-provider                 # working checkout
pi -e npm:pi-free-provider                           # ephemeral, no install

Pinned versions, git refs and install troubleshooting: INSTALL.md.

Update or remove:

pi update npm:pi-free-provider
pi remove npm:pi-free-provider

Sign in

Both sources are optional and independent — install one credential, or both.

/clinefree → Auth

Both routes reach the same free models — a pasted key is not a paid-only path. Pick by preference: a key is a single long-lived string, the device flow keeps tokens rotating and never stores a key.

/zenfree → Auth

Both routes are equivalent for the free tier — the key and the console token are entitled to the same free models, and both are served through the Bun relay, so bun is required either way. Pick by preference: a workspace key does not expire and is trivial to revoke, the device flow refreshes itself.

Credentials live in ~/.pi/agent/clinefree.json and ~/.pi/agent/zenfree.json (mode 0600). They are never written into a pi session, an export, or a repo.

Use

Everything registers as a normal pi provider, so /model, /models, -m, and subagents all work:

The exact current lineup is whatever the live feeds say — ask:

/clinefree → Models
/zenfree → Models

Each entry shows its context window, output cap, and where those numbers came from. All of these models are zero-cost with a daily per-account, per-model quota; hitting it produces a 429, which is a limit, not a credential problem.

Status and refresh

/clinefree → Status
/zenfree → Status

Shows the resolved client contract (the headers/version the upstream CLI sends), feed freshness, the credential (masked), and the account. Press r in the Status panel to force a refresh — otherwise everything refreshes on its own:

The session starts from the last cached lineup; the live refresh runs in the background so a slow feed does not block Pi's prompt. Automatic metadata requests time out after 10 seconds and the complete refresh has a 30-second deadline. Every network path fails soft: an unreachable feed falls back to the last good cache, then to documented defaults, with a warning.

Bun (required for zenfree)

Since the 2026-10-22 gateway change, OpenCode Zen serves free-tier requests only to TLS clients shaped like its own Bun-based CLI. The identical request gets 200 from Bun and 429 from Node, so zenfree spawns a small Bun relay (zen-sidecar.ts) on loopback and sends the request through it; the request shape itself is unchanged.

Two steps:

1. Install Bun: curl -fsSL https://bun.sh/install | bash (Windows: powershell -c "irm bun.sh/install.ps1 | iex").
2. Restart pi, then retry the request. Bun in ~/.bun/bin (%USERPROFILE%\.bun\bin) is also picked up mid-session, because the relay re-resolves Bun on every request.

Resolution order: $ZENFREE_BUN → Bun on PATH (bun.exe/bun.cmd on Windows) → ~/.bun/bin/bun (or %USERPROFILE%\.bun\bin\bun.exe on Windows). If Bun is missing, the extension prints exactly these two steps once and falls back to direct requests — which the gateway will most likely answer with 429. clinefree is unaffected and needs no Bun.

Files and environment

Troubleshooting

Development

npm install
npm test          # vitest, no network — every external call is injectable
npm run typecheck
npm pack --dry-run   # check what actually ships (the Bun relay must be in it)

# live smoke (never in CI): keys come from the environment
CLINEFREE_SMOKE_KEY=sk-… ZENFREE_SMOKE_KEY=oc_sk_… node --experimental-strip-types smoke.ts

Releases are cut by tagging: bump version in package.json, commit, then git tag vX.Y.Z && git push origin vX.Y.Z. The workflow in .github/workflows/release.yml verifies the tag, runs the tests, checks the tarball, and publishes to npm.

License

MIT — see LICENSE.