Get started
Install and open Luvin
Requirements, running Luvin in the browser or as a desktop app, building installers, and what changes between the two versions.
Luvin runs on your computer, in the browser or as a desktop app. There is no backend and no account.
npm install # oncenpm run dev # browser: open http://localhost:5173npm run desktop:dev # desktop appRequirements
Section titled “Requirements”- Node.js 20.19 or later, or 22.12 or later. Check with
node --version. - npm, which comes with Node.js.
- The Luvin project folder on your computer.
Start Luvin
Section titled “Start Luvin”-
Open a terminal in the Luvin project folder.
-
Install the dependencies (once):
Terminal window npm install -
Start the app:
Terminal window npm run dev -
Open
http://localhost:5173in your browser.
The welcome screen appears. To host it for your team, run npm run build: it writes a static site to dist/ that any web server can serve.
-
Open a terminal in the Luvin project folder.
-
Run
npm installif you have not done it yet. -
Start the app:
Terminal window npm run desktop:dev
A Luvin window opens with the same welcome screen.
Build the installers
Section titled “Build the installers”-
In the project folder, run:
Terminal window npm run desktop:build -
Open the
release/folder. The installer is there.
| System | What is built |
|---|---|
| macOS | A .dmg and a .zip |
| Windows | An installer (NSIS) |
| Linux | An AppImage |
Open an unsigned installer
Section titled “Open an unsigned installer”The installers are not signed yet, so your system warns you the first time.
- Drag Luvin to Applications and open it. macOS says it cannot verify the app. Click Done.
- Open System Settings → Privacy & Security and scroll down to Security.
- Next to the message about Luvin, click Open Anyway and confirm with your password.
You only do this the first time. Since macOS Sequoia (15), right-clicking the app and choosing Open no longer skips the warning.
- Run the installer.
- In the warning, click More info.
- Click Run anyway.
Browser or desktop
Section titled “Browser or desktop”Both have the same interface. The differences come from what a browser allows.
| Browser | Desktop app | |
|---|---|---|
| CORS | The API must allow the app’s origin | Does not apply |
Cookie parameters and the Host header |
Not sent: browsers do not allow it | Sent |
| Cookies set by your APIs | Handled by the browser. Luvin cannot read them | Kept by Luvin, which shows and manages them |
| gRPC requests | Not available | Available |
| NTLM authorization | Not available | Available |
| Terminal in Dev Tools | Not available | Available |
| Where a workspace is saved | Browser storage, or a folder on disk in Chrome and Edge | A folder on disk |
| Secrets | Encrypted in the browser with WebCrypto | Encrypted with the operating system’s keychain |
If the API you test does not allow CORS and you cannot change that, use the desktop app.
CORS in the browser version
Section titled “CORS in the browser version”CORS is a browser rule: a web page may call an API on another address only if that API allows it. In the browser version Luvin is a web page, so the rule applies to every call.
The API you test must:
- allow the origin of the app, for example
http://localhost:5173; - list the headers your workflows send in
Access-Control-Allow-Headers.
When a call is blocked, Luvin shows the exact headers to ask for. See Troubleshooting. The desktop app sends the requests itself, so CORS does not apply.