free-piBack home

Changelog

What’s new.

Every free-pi release, in plain language. Update anytime with npx free-pi-cli@latest.

v0.2.7
Changed
  • The model-lock is now reliable and no longer touches your environment. 0.2.6 hid extra providers by deleting their API-key env vars before startup, which (a) missed HuggingFace (its token is HF_TOKEN, not *_API_KEY) and (b) could not hide providers discovered from dual-use credentials (AWS Bedrock, Google Vertex) without also deleting those credentials — which the agent's shell tool legitimately needs. The lock now leaves every credential in your shell intact and instead scopes the model picker to just the free-pi model. Set FREEPI_KEEP_ENV_PROVIDERS=1 to unlock the picker and use your own providers.
v0.2.6
Added
  • /close-other-session — clear a stuck or orphaned session yourself, instead of waiting out the timeout, when you hit "you've already got a free-pi session running somewhere". Force-releases only your own account's session lease; the one-session-per-account limit is unchanged.
  • /whats-new — show recent release highlights on demand.
  • /update — update free-pi-cli to the latest version (a no-op on npx, which is always latest).
  • "What's new" note shown once at startup after you update to a newer version.
Changed
  • The model list is now limited to the free-pi model instead of inheriting every provider whose API key happens to be in your shell (which silently bypassed free-pi). Bring your own key deliberately with /login, or set FREEPI_KEEP_ENV_PROVIDERS=1 to keep your shell's provider keys.
v0.2.5
Added
  • The CLI now shows the model the server is actually serving (accurate status-line label) plus a one-line notice for trial models.
  • Free **Ox Alpha** trial — a frontier preview model, free for the trial period.
v0.2.4
Fixed
  • Moved the Node-version guard into the bin shim so even very old Node versions get a friendly message instead of crashing mid-startup (undici/zstd).
v0.2.3
Added
  • Preflight check for Node zstd support: a clear "upgrade your Node" message instead of a crash mid-request.