Early testing · v0.1.0-alpha.2

Get your first model answering.

Install Eugene Plexus on the computer that will run your models. Then open its console in your browser, choose a model, and try a reply.

This is an alpha. It is ready for early testing, with rough edges still to find. There is no stable release yet. Release notes and known limits.

This update adds scoped application keys, local-only routing, safer failover, encrypted recovery checkpoints and measured shared-load limits. See the tested configurations and Open WebUI and Claude Code setup recipes.

Before you start

A 64-bit Windows or Linux computer, internet access, and a browser. Windows x64 and Linux x64/WSL have been exercised; other hardware has less verification.
For a small first model, aim for 16 GB of RAM and at least 10 GB of free disk space. Larger models need more. A supported GPU helps; CPU inference is available but can be slow.
On Windows, an administrator account or someone who can approve the service installation. On Linux, use your normal account, with curl and a systemd user session.

You do not need to install Python, Node.js, Git, or llama.cpp yourself. The installer fetches Eugene and its Python environment. The console asks before installing the inference engine or downloading a model.

Start with a local model folder. The Windows service runs as the system, so your mapped network drives and saved file-server logins are not inherited. Network storage can be added later in Config → Agent → Storage.

These commands download and run the installer for v0.1.0-alpha.2. You can read the Windows script or read the Linux/Mac script first. The release assets include SHA-256 checksums and the component manifest.

1. Install on Windows

Open PowerShell from the Start menu. Paste this command, press Enter, and approve the administrator prompt when it appears.

Windows install command

irm https://eugeneplexus.com/releases/v0.1.0-alpha.2/install.ps1 | iex

The default install lives in C:\ProgramData\EugenePlexus. It registers a Windows service and starts it. When the installer says Eugene is running, open http://127.0.0.1:8079/ on that computer.

If you already have an older per-user installation, the installer will explain the migration before making changes. Read that message and keep your passphrase available; this first-time guide does not automatically migrate an existing setup.

1. Install on Linux

Open a terminal as your normal user. Paste this command and press Enter. Do not run it with sudo.

Linux install command

curl -fsSL https://eugeneplexus.com/releases/v0.1.0-alpha.2/install.sh | sh

Eugene installs under ~/.local/share/eugene-plexus and starts a systemd user service. Open http://127.0.0.1:8079/. If the installer prints a different address or a manual start command, follow its output.

The service normally starts when you sign in. For startup before sign-in, follow the installer's optional loginctl enable-linger instruction. WSL needs a working systemd user session for automatic startup; otherwise use the manual command it prints and keep that terminal open.

Mac testing

The installer also has a macOS path, but physical Mac verification remains outstanding for this alpha. If you want to help test it, run the Linux/Mac command in Terminal as your normal user. It installs a launchd agent for your login. The experimental MLX adapter is not included.

Mac test install command

curl -fsSL https://eugeneplexus.com/releases/v0.1.0-alpha.2/install.sh | sh

2. Get your first reply

Choose a passphrase. Save it somewhere you can find again. It protects your install; there is no passphrase recovery.
Choose where models live. Accept the proposed folder to start fresh, or choose a folder containing models you already own.
On Home, choose Download and run. Eugene proposes a model for this machine. Check the download size and approve the engine installation when asked. If a model is already on disk, choose Run.
Wait for the model to be ready, then send a message. Downloads and loading appear in Tasks. The first download can be several gigabytes.

To connect another app, use Use from apps on Home. Make a client key, then copy the address, model name and key into your app. Keep the key private.

To try your phone, use Home's Reach switch and the address it shows. Keep both devices on a trusted LAN or VPN; 127.0.0.1 always means the device you are currently using. Finish setup before enabling access from other devices.

Update or repair an install

Read the backup and recovery guide before updating. Alpha.1 needs a complete stopped-install copy for its first upgrade. Alpha.2 includes the encrypted checkpoint procedure; create and rehearse a checkpoint after upgrading.

Running the same command again reinstalls this alpha's Eugene revisions and keeps the existing configuration and model files. The service restarts, so let active requests finish first.

For a later alpha, use that release's instructions. These versioned commands stay on v0.1.0-alpha.2; they do not silently follow development changes. Do not run an older alpha installer over a newer installation. Keep your passphrase and back up the install's configuration before changing versions.

Already running a NAS or Docker control plane?

The matching Linux amd64 image is ghcr.io/eugene-plexus/control-plane:v0.1.0-alpha.2. Keep your existing volumes, port mappings and settings when changing the image tag. It runs the control-plane services; install Eugene on the GPU computer separately. See the container and enrollment guide before creating a new multi-machine install.

Remove Eugene

On Windows, open PowerShell with Run as administrator for the default service install, then run:

Windows removal command

& ([scriptblock]::Create((irm https://eugeneplexus.com/releases/v0.1.0-alpha.2/install.ps1))) -Uninstall

On Linux or Mac, use your normal terminal account:

Linux and Mac removal command

curl -fsSL https://eugeneplexus.com/releases/v0.1.0-alpha.2/install.sh | sh -s -- --uninstall

These commands remove startup registration and the application environment. They leave original model files alone, keep downloaded engines and managed model copies, and move configuration and logs to the backup folder shown in the output. They apply to the default locations above; custom installations need their original prefix.

If something goes wrong

If an update left Eugene unable to start, follow the backup and recovery guide.

The first message says the model is still loading: Home waits for model readiness before enabling Send. If another client connects while the model is loading, wait for Tasks to show it is ready before sending again. A “still coming up” response does not mean the model has crashed.
The page does not open: Use the address printed by the installer, on the same computer. Read the final error and log location in the terminal. On Linux, check systemctl --user status eugene-plexus-agent; on Windows, look for EugenePlexusAgent in Services.
The model will not start or is too slow: Read the problem shown on Home and open Tasks for details. Try a smaller model or a shorter context. A memory-fit estimate is not a speed guarantee.
A network folder is missing: Begin with a local folder. A Windows service needs its own file-server login under Config → Agent → Storage; a drive letter mapped in your desktop session may not exist for it.

Report a problem on GitHub. Include v0.1.0-alpha.2, your OS, GPU and RAM, what you were trying to do, and the error text. Remove passphrases, API keys, private paths and prompts from shared logs or screenshots.