Download BrAIn Edge

If you previously installed with npm install -g @emt/brain-local, the installer above replaces it. Both deploy to the same ~/.flezi-emt folder, so your login, session history, and settings carry over — no re-login needed. Because npm leaves no Add/Remove-Programs entry, the installer can't clean it up automatically, so do this once:

From here on, upgrades are handled by the installer itself — just download and run a newer version. Skipping step 3 is harmless until a later npm update -g, which would fight the installer over ~/.flezi-emt.

If the app installs and opens but sign-in never reaches the login page — and running the daemon in a terminal shows OIDC discovery failed: HTTP 303 — your network reaches the identity provider only through a proxy, and the daemon is not using it. Windows keeps the browser's proxy in a place the daemon never reads, so it connects directly, the network intercepts it, and sign-in fails. Your browser keeps working, which is why nothing else looks wrong.

The script only reads your existing Windows proxy setting and saves it where the daemon can see it — it changes no network configuration and touches nothing in ~/.flezi-emt. If your machine uses an auto-config (PAC) script instead of a fixed proxy, the script says so; open the PAC URL it prints, find the proxy for the identity-provider host, and re-run with -Proxy "<host>:<port>". If your proxy requires Windows (NTLM) authentication, the daemon cannot authenticate to it — ask IT for a proxy allowlist entry for the identity-provider host.

If the installer stops with “This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.” (MSI error 1619), an earlier uninstall left the product registered with Windows while its cached installer was deleted. Windows then tries to remove that leftover before installing, can't open it, and gives up — so neither installing nor uninstalling works until the registration is cleared.

Your ~/.flezi-emt folder — login, session history and settings — is never touched. If the script finds nothing, the downloaded .msi is corrupt instead (a 400+ MB download through a corporate proxy is the usual reason): check its SHA-256 against the checksum shown with the download.

If emt-brain --version prints the version you just installed but 127.0.0.1:3737 still shows an older one — often an older channel too — the installer placed the new program but the step that replaces the deployed files did not finish. Uninstalling does not remove ~/.flezi-emt, so the previous payload is still there and still running. This is most common when going back to a stable build after using a canary one.

Your databases are kept: the script removes only the deployed program files, never dbs, .brain-local, or any per-project .flezi-emt folder. It also writes the install logs it collected to a folder on your Desktop — please send that folder when reporting this.