---
title: "Neural Inverse Build"
---

# Neural Inverse Build

The Editor, the Agents app and the CLI, what each is for, and how they work with your organisation's Govern deployment.

Neural Inverse Build is the engineer-facing product: three apps that sign in to the same account and decide agent actions with the same policy engine.

| App | What it is for |
|---|---|
| [Editor](https://neuralinverse.com/docs/editor/) | Hands-on development with AI assistance: inline completions, chat, and edits you review line by line. |
| [Agents](https://neuralinverse.com/docs/agents-app/) | Delegating work to agents, running several sessions in parallel, and reviewing their changes. |
| [CLI](https://neuralinverse.com/docs/cli/) | An AI coding agent for the terminal, interactive or scripted, including in CI. |

The Editor is built on Code - OSS, the open-source core of Visual Studio Code. Build is proprietary, licensed under your agreement with Neural Inverse, and is pre-release: interfaces and data formats may change between versions.

## How Build works with Govern

When you [sign in](https://neuralinverse.com/docs/get-started/sign-in/), the apps work with your organisation's Neural Inverse Govern deployment:

- **Models.** In the Editor and the Agents app, organisation-approved models are reached through Govern's model gateway, with your own sign-in. See [Models](https://neuralinverse.com/docs/build/models/).
- **Policy.** Your organisation's signed policy decides what agents may do on your device. See [Policy, approvals and audit](https://neuralinverse.com/docs/build/governance/).
- **Audit.** The Editor and the Agents app keep a tamper-evident record on the device of what people and agents did. Nothing leaves the device unless your organisation turns uploading on, and then only to your organisation's own Govern deployment. The CLI writes its own audit log when it is turned on. No telemetry is sent to Neural Inverse.

Whatever must hold is enforced by Govern, where it applies whatever client is used. The checks in the apps are a second line of defence, because a modified build can remove them.

## Domain modules

For engineering work that usually lives in vendor tools (firmware, FPGA and HDL, PLCs, distributed control systems, mainframe, substation automation, automotive networks), the Editor has [domain modules](https://neuralinverse.com/docs/build/domain-modules/). They are at different stages of verification; that page states each one's state.

## Pages in this section

- [Editor](https://neuralinverse.com/docs/editor/)
- [Agents](https://neuralinverse.com/docs/agents-app/)
- [CLI](https://neuralinverse.com/docs/cli/)
- [Models](https://neuralinverse.com/docs/build/models/)
- [Policy, approvals and audit](https://neuralinverse.com/docs/build/governance/)
- [Domain modules](https://neuralinverse.com/docs/build/domain-modules/)