Install Lispex
Download the Native executable for your operating system, or install it with one command.
Download file version v1.21.3
Install with one command
# macOS / Linux
curl -fsSL https://www.lispex.com/install.sh | sh
# Windows (PowerShell)
irm https://www.lispex.com/install.ps1 | iexThe install script finds the latest release when it runs and compares the downloaded executable with the SHA-256 checksum file published beside it.
Check the version
Open a new terminal and run this command. Native prints its name and version.
lispex --versionlispex 1.21.3If the command is not found
- macOS and Linux install to ~/.lispex/bin by default. Add that directory to PATH, then restart the shell.
- Windows installs to %LOCALAPPDATA%\Lispex\bin by default. Add that directory to the user PATH, then open a new PowerShell window.
Install in a project with npm
With Node 18 or newer, install the npm package in your project folder.
npm install lispexCheck the version with npx in the same folder. npx runs the lispex command installed in that folder. The npm package prints only the version number.
npx lispex --version1.21.3Save this program as hello.lspx in the same folder.
(define language "Lispex")
(list 'hello language (+ 2 3))Run the file with npx. The command prints this result, exits with status 0, and creates no files.
npx lispex hello.lspx(hello "Lispex" 5)To use the lispex command in any folder, you can also install the package globally. If Native is also installed, the lispex command runs the product whose directory comes first on PATH.
npm install -g lispexIf the command is not found, confirm that Node 18 or newer is active and that the global npm binary directory is on PATH.
Use Lispex without installing
The Playground runs Lispex in your browser with nothing to install. First Program starts in the Playground, so you can follow it before you install.
Other distributions
Choose where to run
| Task | Product | Run a source file |
|---|---|---|
| Try code in the browser | Playground | Paste the source and run it |
| Run files in a Node.js project | npm package | npx lispex hello.lspx |
| Run a downloaded executable | Native | lispex hello.lspx |
All three use the Lispex Interpreter by default. In a terminal, a successful run prints its result, exits with status 0, and creates no files. The product is what you install or open. The execution method is how that product runs the program.
- Choose Native for the widest set of tools. It includes the Lispex Interpreter, a resource-controlled rule engine, the Lispex VM for verified bytecode, intermediate-form commands, exact Lispex Images, and the complete Lispex Vouch workflow. Native issues evidence, reruns the pinned request, and runs the local gate. It can also derive a compiled artifact from the same exact source and record Lispex VM agreement.
- Choose npm when Node is already available. It runs source, provides the same exact Lispex Image commands through Rust compiled to WASM, authenticates Vouch evidence with the same checker as Native, and replays decision corpora offline. Intermediate forms, verified bytecode, the Lispex VM, evidence issuance, current re-execution, and the local gate need Native.
- Use the Playground to run source and to create, open, page through, recover, download, and explicitly run exact images directly in your browser. Native provides intermediate forms, bytecode, and the Lispex VM, while Native and npm provide the Vouch artifact and policy tools.
All platforms
Every release file and checksum is also on GitHub Releases. The npm package and the native executables are both under the Apache License 2.0, and each release includes a notices file for the bundled libraries.
Download file version v1.21.3
| Platform | Binary | Checksum |
|---|---|---|
| Linux · x86_64 | lispex-linux-x86_6425.1 MB25,118,456 bytes | .sha256 |
| Linux · aarch64 | lispex-linux-aarch6416.8 MB16,835,384 bytes | .sha256 |
| macOS · Apple silicon | lispex-macos-aarch6420.9 MB20,946,992 bytes | .sha256 |
| macOS · Intel | lispex-macos-x86_6424.3 MB24,324,284 bytes | .sha256 |
| Windows · x86_64 | lispex-windows-x86_64.exe23.1 MB23,114,752 bytes | .sha256 |
| Release manifest | manifest.json | file names, sizes, addresses, and SHA-256 checksums |
A checksum identifies the exact bytes you downloaded. On macOS or Linux, keep the executable and its .sha256 file in the same folder and run this command. It prints OK when they match.
# Linux
sha256sum -c lispex-linux-x86_64.sha256
# macOS
shasum -a 256 -c lispex-macos-aarch64.sha256In Windows PowerShell, run these two lines. The second prints True when they match.
$want = (Get-Content .\lispex-windows-x86_64.exe.sha256).Split(' ')[0]
(Get-FileHash .\lispex-windows-x86_64.exe).Hash -eq $wantOn Windows, you can also run the downloaded file from its folder without installing it, with hello.lspx in the same folder.
.\lispex-windows-x86_64.exe hello.lspxEditor extension
The official studiohaze.lispex extension recognizes .lspx files and adds syntax highlighting and the Lispex file icon for light and dark themes.
Visual Studio Marketplace · Open VSX Registry
Formatting requires Native. Format Document and format-on-save pass the document to lispex fmt - and use the formatted source it returns. If lispex is not on PATH, set lispex.format.executable to its location.
Developer components
The resource-controlled rule engine, exact bytes
Applications can pin the exact bytes of this engine. It runs one rule under the declared resource profile. Its manifest fixes capabilities, metering, value exchange, receipt fields, memory limits, and checksum. Recorded request and result bytes let every consumer compare the exact observation.
| Item | File | Checksum |
|---|---|---|
| Resource-controlled rule engine WASM | lispex-embed-evaluator.wasm1.6 MB1,588,220 bytes | .sha256 |
| Rule engine manifest | lispex-embed-evaluator-manifest.json26.3 KB26,347 bytes | .sha256 |
| Recorded request and result bytes | lispex-embed-evaluator-golden-vectors.json4.0 KB4,014 bytes | .sha256 |
| Rule engine redistribution package | lispex-embed-evaluator-redistribution.zip15.0 MB14,994,343 bytes | .sha256 |
The whole-language rule engine, exact bytes
A separate component covers the complete lispex-profile-1.5 and carries its own capability, metering, component, and artifact identities. It reuses the established value exchange, run transcript, and portable record format. Native selects it through explicit embed full commands and creates a fresh instance for every operation.
| Item | File | Checksum |
|---|---|---|
| Whole-language rule engine WASM | lispex-full-embed-evaluator.wasm1.6 MB1,588,667 bytes | .sha256 |
| Whole-language rule engine manifest | lispex-full-embed-evaluator-manifest.json2.5 KB2,465 bytes | .sha256 |
| Recorded vectors for the whole-language engine | lispex-full-embed-evaluator-provider-vectors.json14.7 KB14,663 bytes | .sha256 |
| Redistribution package for the whole-language engine | lispex-full-embed-evaluator-redistribution.zip15.1 MB15,128,596 bytes | .sha256 |
Typesetting rule workspace
Send a heading placement decision to the printer
Prepare a rule and input, sign its decision, and let the recipient authenticate and rerun it. The guide includes the complete files and commands.
Related pages
- Connect the MCP Server. Native also includes lispex mcp serve, a local MCP server for language lookup, diagnostic explanations, and trusted-source evaluation within size and time limits.
- Create and Restore Lispex Images. Store exact source in a PNG or ZIP file and recover it byte for byte in Native, npm, or the Playground.
- Lispex Vouch. Native authenticates a signed decision, reruns it with the source and input you supply, and records a local gate result. Your application decides the action.
- Products and Supported Platforms. Lists the features of each product and what a download check establishes.