Private-alpha setup

Private-alpha setup

Authorized source access required

LM Nexus is not publicly downloadable yet. These commands assume you already have access to the LM Nexus application repository.

Native Windows PowerShell

Native Windows PowerShell is the current primary development and best-validated path.

From the repository root:

powershell -ExecutionPolicy Bypass -File scripts\setup-dev.ps1
.venv\Scripts\python.exe scripts/dev-doctor.py
.venv\Scripts\python.exe run.py

Native Windows uses the ConPTY/pywinpty Terminal path. The current full-stack validation has exercised the launcher, backend/frontend, registered modules, Terminal, Agent Runtime, Model Manager, durable run state, and process cleanup together on a real native-Windows host.

Linux or WSL

Linux and WSL setup/startup paths remain available as portability/compatibility paths:

./scripts/setup-dev.sh
.venv/bin/python scripts/dev-doctor.py
.venv/bin/python run.py

The setup script creates the virtual environment when needed, installs backend and frontend dependencies, uses the repository lockfile, and copies example environment files if they are missing.

It also checks the exact toolchain versions instead of silently replacing them behind your back.

Linux and WSL have not had the same recent maintainer validation as native Windows, so treat them as paths that still need fresh parity validation rather than the recommended Windows route.

Primary launcher

run.py is the main way to start LM Nexus from source.

Alternative wrappers remain available for Linux/WSL and Windows-to-WSL workflows, but the current primary development path is native Windows PowerShell.

Expected local services

The development UI is normally available at:

http://localhost:5173

The backend listens on port 8000 by default.

If dev doctor fails

Do not fix a version or environment check by randomly changing packages inside the repository.

Fix the problem the doctor reports, then run it again.

Continue with Quick start.