# Download

> The Editor, the Agents app and the CLI: the platforms they run on, what installs, and how sign-in works. Installers are provided to your organisation with access.

Source: https://neuralinverse.com/download/

---

![](/photos/bench.jpg)

Download

# The Editor, the Agents app and the CLI.

Installers are provided to your organisation once it has access, together with the address your apps sign in to.

Editor and Agents app

macOS, Windows, Linux

CLI

macOS, Linux, Windows

Installers

From your administrator

Sign-in

Your organisation account

Editor and Agents app

## Two desktop apps, installed together.

- **What installs:** Two desktop apps, installed together: the Editor (named Neural Inverse on your system) and the Agents app (Neural Inverse Agents). Each has its own icon, process and data folder, and either runs on its own.
- **Platforms:** macOS, Windows and Linux.
- **Where it comes from:** Your administrator provides the installer for your organisation, with the address of your Govern deployment if the build does not already contain it.
- **Reviewing the source:** The apps are proprietary. Under a non-disclosure agreement, your security team can review their source code.

CLI

## An AI coding agent for the terminal and CI.

- **What installs:** The command neuralinverse, with the short alias ni. It installs on its own, separately from the desktop apps.
- **Platforms:** macOS on x64 and arm64; Linux on x64 and arm64, and musl-based distributions on x64; Windows on x64.
- **Two ways to install:** With npm on Node.js 22.19 or newer, or as a standalone binary that needs no Node.js. Your administrator gives you the installer address when your organisation has access.
- **Checked before it installs:** The installer verifies the binary against the release's published checksums and refuses to install on any mismatch or missing checksum. It does not edit your shell profile.
- **Closed networks:** Your administrator can host the release files and checksums on an internal mirror and point the installer at it.

Sign-in

## Sign in to your organisation, nowhere else.

- **Your organisation's deployment:** Each app signs in to your organisation's Govern deployment with your own account. Your administrator sets which deployment, through managed policy or managed settings.
- **Checked first:** Before sign-in, the app verifies the deployment's region document and issuer over HTTPS and pins the issuer. Tokens are only sent to the deployment that issued them.
- **In the browser:** OAuth 2.0 with PKCE: your browser opens your organisation's sign-in page and returns to the app.
- **Without a browser:** On a machine with no browser, such as over SSH, sign in with a device code (RFC 8628) and approve it on any device that has one.
- **Where the session is kept:** In the operating system's credential store: Keychain on macOS, DPAPI on Windows, the Secret Service on Linux.

Get the apps

## Available by request.

Neural Inverse Build is pre-release, and there are no public download links. If your organisation has access, ask your administrator for the installers. If it does not, request access and we will talk with your team.

[Request access](https://neuralinverse.com/contact/?topic=access)[Sign in](https://neuralinverse.com/sign-in/)

[Installation guide](https://neuralinverse.com/docs/get-started/install/)[Sign-in guide](https://neuralinverse.com/docs/get-started/sign-in/)

![](/photos/team.jpg)

## Talk to our team.

Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation.

[Request access](https://neuralinverse.com/contact/?topic=access)[Contact us](https://neuralinverse.com/contact/)
