Neural Inverse Build
Documentation

Version Latest

CLI

The Neural Inverse CLI is an AI coding agent for the terminal. This overview covers what it does, how to start, and where each topic is documented.

The CLI is the terminal part of Neural Inverse Build. It is an AI coding agent: it reads your code, runs commands and makes changes, with the model provider of your choice, under permission rules that you and your organisation control. The command is neuralinverse; ni is a short alias.

you  │ the refund endpoint returns 500 when the order has no payment, find and fix it
ni   │ The handler assumes `order.payment` is always set. Let me look at the route first.
  ⬢ search_text refund · 3 files · 41ms
  ⬢ read_file src/routes/refunds.ts · 212 lines · 2ms
┌─ approval needed ─ edit_file
│ Edit src/routes/refunds.ts
│   48 - const captured = order.payment.capturedAmount;
│   48 + if (!order.payment) return res.status(409).json({ error: 'order has no payment' });
└─ [1] allow once  [2] always allow…  [3] deny  [4] deny & explain

What it does

  • Any model provider. Anthropic, OpenAI (Chat Completions and Responses), Google Gemini, AWS Bedrock, Claude on Vertex AI, Azure OpenAI, and any OpenAI-compatible server such as Ollama, vLLM, LM Studio, OpenRouter, Groq, DeepSeek, Mistral or xAI. Local models need no key.
  • Every action checked first. Each file change and command passes your organisation's governance, then permission rules and a mode (ask, auto-edit, read-only, full-auto). Shell commands can run in an operating-system sandbox.
  • Built for teams. Layered settings, managed policy files, an append-only audit log, hooks, MCP servers, skills, sub-agents and slash commands kept in the repository.
  • Scriptable. A non-interactive mode with text, json or stream-json output for scripts and CI, a GitHub Action, an SDK and a local HTTP API.
  • Recoverable. Sessions are saved and can be resumed; every prompt is a checkpoint you can return to with /undo.

Quick start

Install the CLI, set a key for a model provider (or run a local model), and start it in your project folder:

export ANTHROPIC_API_KEY=...        # or OPENAI_API_KEY, GEMINI_API_KEY, OPENROUTER_API_KEY, ...
cd your-project
neuralinverse

Started with no usable provider, the CLI walks you through setup. A local model works without a key:

ollama pull qwen3-coder
neuralinverse --model ollama/qwen3-coder

Run once without the interactive interface:

neuralinverse -p "summarize what changed in the last 5 commits"
git diff | neuralinverse -p "review this diff for bugs" --output-format json

To use your organisation's account and policy, sign in to Govern with neuralinverse login. Signing in is optional unless your organisation requires it.

Developer environments

The CLI has the same two optional developer environments as the Editor: embedded for Cortex-M firmware and hdl for FPGA and ASIC designs. An environment is a project setting you choose by hand; it is never switched on automatically. See Firmware and hardware environments.

Find your way

TaskPage
Install, update and check the installationInstall and update
Sign in with your organisation's accountSign in to Govern
Learn the screen, keys and approval cardsYour first session
Look up a slash commandSlash commands
Resume, undo, export; keep long sessions smallSessions and context
Choose providers and models, set budgets and fallbacksProviders and models
See what the agent can doTools
Control what runs without askingPermissions and modes
Write settings filesSettings reference
Run scripts at lifecycle pointsHooks
Connect MCP serversMCP servers
Add project instructions, commands, agents and skillsInstructions, commands and skills
Share a packaged workflowPlugins
Use organisation context from GovernOrganisation context
Gate agent edits and commits on your rulesChecks
See what is reported to your organisationActivity record
Run in scripts and CINon-interactive use and CI
Run unattended goals, team runs and schedulesGoals, team runs and schedules
Work with GitHub pull requests, issues and ActionsGitHub
Use the agent from Zed or VS CodeEditors
Firmware and HDL workFirmware and hardware environments
Drive the agent from codeSDK, server and embedding
Use a browser instead of the terminalWeb interface
Roll out to an organisationEnterprise deployment
Measure the agentEvals
Look up a command, flag or exit codeCommand reference
Fix a problemTroubleshooting

Maturity

The CLI is at version 0.1.0, with further features listed as unreleased in its changelog. Some parts are not complete:

  • Organisation policy from Govern. After sign-in the CLI asks Govern for a signed policy at GET /api/v1/policy/bundle. The current Govern server does not serve that route, and the CLI treats a missing policy as "no organisation policy". Until it does, organisation settings, allowed models, the organisation model gateway and organisation skills do not reach the CLI through sign-in. Managed settings files and the remote policy work today. See Sign in to Govern.
  • Activity record to Govern. Govern's current ingest route expects a service credential and a different request body from the one the CLI sends, so delivery of the CLI's activity events to Govern is not confirmed end to end. A self-hosted receiver works as documented. See Activity record.
  • Firmware and HDL tools. They reuse the Editor's modules, whose own records say nothing has been run on a board yet. See Firmware and hardware environments.
  • Evals. No real-model results have been recorded yet. See Evals.
  • Running inside the Editor. The adapter that registers the CLI as an agent in the Editor's shared agent host is drafted but not yet part of the Editor. See SDK, server and embedding.

Licence

The CLI is proprietary and licensed under your organisation's agreement with Neural Inverse. Its package includes a NOTICE file listing the open-source libraries it uses and their licences. See licence.

For the other Build apps and for Govern, see Neural Inverse Build and Neural Inverse Govern.

Last reviewed 17 October 2026View as Markdown

CLI · Docs · Neural Inverse