- Version
- 1.0.0
- Build
- Alpha 3
- Size
- 437 KB
- SHA-256
59c2566f5c13764f1a90454f7155a3a95314bae5af2b373a6c9e26b8f2aceeb5
Done this before? Unzip, then load the folder as an unpacked extension: chrome://extensions or opera://extensions, Developer mode, Load unpacked.
View source on GitHub. This is the whole free extension under GPL-3.0, and it is the tree this build was compiled from.
Installing it
- Unzip it
Unpack the archive somewhere you will not delete by accident, like your documents folder. Chromium loads the extension from this folder every time the browser starts, so moving or deleting it later uninstalls the extension.
- Open the extensions page
Typing it into the address bar is the reliable way; some browsers hide the menu entry.
- Chrome
chrome://extensions - Edge
chrome://extensions - Brave
chrome://extensions - Opera GX
opera://extensions
- Chrome
- Turn on Developer mode
The toggle is in the top right. Nothing below appears without it.
- Load unpacked
Click Load unpacked and select the folder you unzipped. Select the folder itself, the one directly containing
manifest.json, not its parent and not the zip.
If it does not appear
The usual cause is dragging the .zip onto the extensions page. That looks like it should work and does nothing useful: Chromium accepts a packed .crx or an unpacked folder, and an archive is neither. Unzip first.
The second most common cause is selecting the wrong folder. If unzipping produced a folder containing another folder of the same name, the one you want is the inner one, the one with manifest.json directly inside it.
What to expect from a hand-installed build
- An unpacked-extension warning
- Chromium shows a “disable developer mode extensions” prompt on startup. That is the browser reacting to how it was installed, not to anything about this extension, and it stops once the store version is live.
- No automatic updates
- A store install updates itself. This one does not. To move from an earlier alpha, download this file, unzip it over the old folder, then press reload on the extension’s card at
chrome://extensions. Your sessions survive that; they live in the browser profile, not in the folder. - It has not been through store review
- Which is exactly why the source is worth reading rather than trusting.
What is in the file
This is the free build, and that is a property of the artifact rather than a promise about it. Open manifest.json after unzipping: "nvx_tier": "free" is stamped there by the build, no licence endpoint or verification key is present, and the paid code is not in the bundle to be unlocked. A pasted licence token does nothing in a build with no key to check it against.
Checking you got the file we published
Run one of these in the folder you downloaded to, and compare the result with the SHA-256 above. If it does not match, do not install it.
Get-FileHash nvx-session-1.0.0.zipshasum -a 256 nvx-session-1.0.0.zipTelemetry, in this build
This is a packaged build, so it carries a telemetry endpoint. That does not mean it sends anything: consent is the other gate and it starts off. No usage stats leave your machine unless you turn them on, and what it collects lists everything it could send if you did.