Windows
The Codifix v3.0.0 release includes unsigned x86_64 preview packages. The published v2.1.0 assets install the previous Memory Layer product, not Codifix. Windows ARM64 is not a release target.
Preview packages
The published release assets are:
codifix-3.0.0-windows-x86_64-build.2.msicodifix-3.0.0-windows-x86_64-build.2.zipcodifix-3.0.0-windows-x86_64-build.2-server-tools.msi
Download from the release page and verify its SHA256SUMS. The MSI and ZIP provide client/operator tools; the separate machine-level server-tools MSI is a scaffold and does not provision dependencies or start services. This preview does not provide the complete native PostgreSQL/PDS/Pi stack or full Windows parity.
The release is a breaking product rename. For an existing Memory Layer installation, follow the Update guide and the release-specific reinstall procedure before replacing it.
MSI
Download and verify the per-user MSI, then run it. The
installer places codifix.exe, the bundled web UI, skill templates, README,
example config, and PowerShell completion under
%LOCALAPPDATA%\Programs\Codifix, then adds its bin directory to the user
PATH.
codifix --version
codifix wizard --global
codifix doctor
codifix health
codifix tuiThe native package does not include PostgreSQL. Use a PostgreSQL server with pgvector, a local database you manage yourself, or the bundled Docker Compose stack where supported.
Portable ZIP
Extract the verified ZIP, add its directory to PATH, then run:
codifix --version
codifix doctorDocker Desktop
The bundled Compose stack runs under Docker Desktop:
git clone https://github.com/3vilM33pl3/codifix
cd codifix
docker compose upThat brings up PostgreSQL with pgvector, the Codifix service, and the web UI at http://localhost:4040. Load the showcase project from inside the container:
docker compose exec codifix codifix demoWSL2
For Linux-native shell behavior, TUI workflows, and file watchers, use an Ubuntu WSL2 distribution and follow the Linux / Debian install inside it.
Repositories are reachable from WSL2 under /mnt/c/..., though keeping active
repositories inside the WSL2 filesystem is faster and works better with file
watchers.