Percher 1.0: one version, a clear licence boundary

Percher's six public npm packages established a shared 1.0.0 baseline on 13 September 2026, making the licence boundary clear across the CLI, local MCP server and JavaScript libraries. The same-day 1.0.1 patch is now the latest release for CLI, MCP, core and client. Shared and toml remain at 1.0.0.

Update the tools you use

For the CLI, run the 1.x version without a global install:

npx --yes percher@1 --version
# Or, with Bun:
bunx percher@1 --version

If you installed the CLI globally, update it with npm install -g percher@1. For a local MCP configuration, use @percher/mcp@1 in the existing npx arguments and restart that MCP server. The MCP guide shows the configuration. A hosted connector at https://mcp.percher.app/mcp does not need a local package update.

The release includes the existing 53 local MCP tools and 30 app starters. We verified the published packages with fresh Node and Bun installations, including MCP startup and generated project files.

The 1.0.1 preview warning update

CLI help, MCP tool descriptions and client declarations now explain that previews share the live app's PocketBase and persistent files in /app/data. Executed preview code can write to that shared data. Discarding a preview or leaving the live version unchanged does not undo those writes; use isolated data when you need an isolated test.

The update clarifies these instructions without changing deployment behavior. The mixed 1.0.1/1.0.0 package set passed fresh installations directly from npm under Node and Bun, including MCP's 53 tools and generated app files.

A clear licence boundary

All six packages use FSL-1.1-MIT from 1.0.0 onward. Versions below 1.0.0 retain their original MIT licence. FSL is a source-available licence with use restrictions and an additional MIT grant two years after each version is first made available under FSL. Read the LICENSE shipped with your chosen version for the complete terms.

Older npm versions now display an upgrade notice explaining that boundary. Deprecation does not withdraw their MIT grants or change their archived code.

The files Percher generates for your project have their own permissive licence: Percher-authored app scaffolds and AI instruction files use 0BSD. Your existing project files keep their existing licences, and bundled third-party components keep theirs. The package licence does not relicense those files.

See Package versions and licences for the six-package list, installation examples and how to handle an old-version warning.

This is a release of the public developer tools. Beta availability is announced separately. General signup and paid checkout remain closed.