Download

Releases up to 0.9.0 named their archives Chrysalis-<version>-<system>. Internal names stay (chrysalis command, CHRYSALIS_*, data folders) so installs keep working.

First start

1. Download the file for your system from the table above.
2. Start it. Your browser opens a one-time setup page; create your account there (it is local, it never leaves your machine).
3. Add a model in Settings > API connections.
4. The welcome screen offers Roleplay: install it in one click. Or open Molfar and ask him for something.

Windows from source in one file

On Windows you can also run from source with one file: put Molfar-Vertep.bat (in the repository root) in any folder and double-click it. It installs Git and Bun if they are missing, downloads Molfar Vertep next to itself, offers each new release before installing it, builds what changed, offers a desktop shortcut and opens Molfar Vertep in your browser. Molfar-Vertep.bat dev follows the newest work in progress instead of releases. Folder names with spaces or in any language are fine.

If Git says the folder has dubious ownership (another Windows user owns it: common on a second drive, a USB stick, or a folder made as administrator), the launcher stops and offers to trust that one folder. To do it yourself, run git config --global --add safe.directory "D:/path/to/Molfar-Vertep" with your folder's path (forward slashes), then start the launcher again.

macOS

Start with start.command, not chrysalis. These builds do not carry a signature macOS accepts, so opening chrysalis directly is blocked or closes straight away with killed. start.command clears the download flag, signs the program for that Mac and starts it; use it again after each update.

Android

The Android APK is debug-signed, so it cannot update an installed copy: remove the old app first. Export your apps' backups before that, because uninstalling deletes the app's data.

Docker

From version 0.3.0 the release workflow publishes ghcr.io/molfarwav/molfar-vertep (tags latest and the version). Settings and data live in the /chrysalis volume, and the container listens on port 8788.

docker run -d --name chrysalis -p 8788:8788 -v chrysalis-data:/chrysalis \
  ghcr.io/molfarwav/molfar-vertep:latest
docker logs chrysalis        # the first start prints the setup link

The repository's docker-compose.yml does the same; docker compose up -d --build builds an image from your checkout instead of pulling one.

Run from source

You need Git and Bun 1.4 or newer.

git clone https://github.com/MolfarWav/Molfar.Vertep
cd Molfar.Vertep
bun install
(cd client-agent && bun install)
bun run build:client
bun start

bun run dev restarts on every change. bun run test runs the tests and bun run typecheck checks every project.

Updating

• Downloads (Windows, macOS, Linux, portable): the engine's update button downloads the new version, restarts and reloads the page. It is also in Settings > Server.
• Apps: the Updates button in the top bar shows a badge when anything is newer. Apps you have changed are never overwritten: updating merges the new version with your edits.
• Android: remove the old app and install the new APK.
• Docker: docker pull ghcr.io/molfarwav/molfar-vertep:latest, then remove and recreate the container with the same volume.
• From source: git pull && bun install && (cd client-agent && bun install) && bun run build:client, then restart.

Molfar Vertep keeps your data in its own folder, so an update never touches it.