Installation

Three supported paths. Pick one — they do not mix.

Path 1 — End users: packaged Windows release (no Python)

Download NexusScalpEngine-<version>-win-x64-setup.exe (or the portable ZIP NexusScalpEngine-<version>-win-x64.zip) from GitHub Releases. The installer bundles the full Python runtime (PyInstaller) — you never touch Python, pip or PyTorch.

One command (recommended)

iex (irm https://raw.githubusercontent.com/Opselon/NexusTradingForexBot/main/installer/install-release.ps1)

That downloads the release installer, verifies the payload against its published SHA-256 digest before installing anything, runs the per-user installer (no admin), then makes the installed build prove itself (verify-release). Nothing is installed unless every check passes. Useful variants:

# pin an exact release (skips the GitHub API lookup entirely - use this on
# rate-limited or locked-down networks)
iex (irm https://raw.githubusercontent.com/Opselon/NexusTradingForexBot/main/installer/install-release.ps1) -Version 9.1.0

# portable ZIP instead of the setup.exe
iex (irm https://raw.githubusercontent.com/Opselon/NexusTradingForexBot/main/installer/install-release.ps1) -Portable

# see exactly what would happen: no download, no install, no mutation
iex (irm https://raw.githubusercontent.com/Opselon/NexusTradingForexBot/main/installer/install-release.ps1) -DryRun

Full parameter and exit-code reference: docs/INSTALL_WINDOWS.md.

Manually

1. Run the installer (per-user, no admin) or unpack the portable ZIP.
2. First run opens the setup wizard (nexus setup): compatibility report →

mode (default: PAPER, never silently LIVE) → symbol → health check.

1. User data (config/logs/databases/models) lives in

%LOCALAPPDATA%\NexusScalpEngine and survives upgrades, repairs and uninstalls.

Path 2 — PowerShell bootstrap installer (no Python, no Git, no admin)

Downloads and provisions everything user-scoped (Python via uv, Git if missing, engine source from GitHub, a managed venv, dependencies, the nexus command on PATH) with safe-update, repair, recovery and a machine-readable stage protocol:

iex (irm https://raw.githubusercontent.com/Opselon/NexusTradingForexBot/main/installer/install.ps1)

The installer enforces download→install integrity at every step: artifacts are verified (size floor, optional SHA256 pin) before being committed, partial downloads are never installed, verification failures BLOCK the install with a precise reason, and every download's digest + outcome is recorded in state\install.json. The full truth table (AVAILABLE / DEGRADED / BLOCKED) is documented in docs/INSTALL_INTEGRITY.md.

.\install.ps1 -DryRun      # show the plan as JSON, mutate nothing
.\install.ps1 -Manifest    # list the installer's 12 stages (JSON)
.\install.ps1 -Repair      # repair runtime without touching user data
.\install.ps1 -Commit sha  # reproducible pin (Commit > Tag > Branch)

Installs under %LOCALAPPDATA%\Nexus (override with -NexusHome); user config in %LOCALAPPDATA%\Nexus\config always survives reinstall/updates. Full parameter reference: docs/INSTALL_WINDOWS.md · architecture: docs/INSTALLER_ARCHITECTURE.md.

Path 3 — Developers: from source

git clone https://github.com/Opselon/NexusTradingForexBot.git
cd NexusTradingForexBot
python -m venv .venv
# Windows PowerShell:
.\.venv\Scripts\Activate.ps1
# Linux/macOS:
source .venv/bin/activate

pip install --upgrade pip
pip install -e ".[dev]"

# Smoke-test the whole toolchain — no broker needed
pytest tests/unit -q

• Python 3.11.x is required for a source run (not needed for the packaged release).
• Windows 10/11 x64 for the native MT5 adapter. **ARM64 is explicitly

unsupported** (PyTorch/Polars/MetaTrader5 ship no ARM64 wheels); nexus doctor reports this.

• Linux x64 is developer/Docker (remote-gateway adapter) only.

Next step

→ Quickstart