Lila Modeler 1.0.0-beta.18

Release notes for the third public beta of the desktop app. It attaches a macOS installer and a Windows installer that has not been tested on a real Windows machine yet. The web app and the @lila-modeler/engine package on npm move to the same version.

What is new since beta.1

beta.2 to beta.15 and beta.17 were interim versions (no installer attached); beta.16 was the first with installers. This is everything they added, by topic. The exact per-version list is in the changelog.

• Beta 18: agents use the whole system. The MCP server has 16 tools and the CLI new process, scenario and export commands, all on the same .lila files: create a process from an outline, edit it, annotate it, simulate it, import a scenario sheet and export the diagram, document and results with no app. A lock shared across processes refuses a busy file (E-ARCHIVO-OCUPADO), and the open desktop app reloads when the file changes on disk. The simulation runs the process the scenario targets, not the first pool.
• Beta 17: Simulate phase 2. A finished run stays in Simulate and a dock under the canvas (Cmd+J / Ctrl+J) shows quick results, bottlenecks, the run log and warnings, with Open in Results and Export CSV. The Simulate steps are now Parameters, Resources, Calendars and Arrivals, Results can be detached to its own window, plain T no longer toggles the token animation, and undoing the delete of a pool keeps the simulation intact.
• Beta 16: platform docs (what is tested and what is not, per platform), the Windows installer attached to the release with a tester guide, validation messages fully in one language, lanes in the process document grouped by id, and fixes: the process document no longer mixes two processes, a pasted pool gets its own process, Save As refuses a folder holding another project's processes, and the welcome hints show Ctrl outside macOS.
• Modelling and the diagram
  • Several processes in one project, each a tab on the canvas (+ to add one), with call activity navigation and a «Back to …» crumb.
  • Colours per element, align and distribute tools, and a full BPMN palette. Constructs the engine does not simulate now warn while you model and only block Run.
  • Extended attributes per element type, filled in per element and shown in the process document.
  • The diagram exports as SVG, PNG and PDF and prints from the File menu; BPMN ids are hidden behind an «Advanced» setting; bpmn-js speaks Spanish.
• Simulation and results
  • Calendars with Bizagi-style day presets and from–to ranges, monthly and annual recurrence and holidays.
  • Scenario parameters from Excel/CSV: download a filled-in template, edit it, import it back with a report of every change before anything is applied, and undo.
  • Bar charts under the Results and Compare tables; clearer messages when Run cannot start (empty process, warm-up longer than the arrivals, entries for deleted elements) and a button to remove orphan scenario entries.
• Deliverables
  • The process document exports to Word (.docx) and to one printable HTML page, laid out the way Bizagi's «Publish to Word» does.
  • An examples gallery on the welcome screen: the restaurant order, Bizagi's four simulation levels and the M/M/1 and M/M/3 oracles.
• Desktop app
  • Autosave with recovery after a crash, a File menu in the top bar, a detachable scenario window, hideable and resizable panels, a command palette (Ctrl+K / ⌘K), one shortcut map with a Settings section, and standard macOS keys (⌘W, ⌘Q, Help menu).
  • A notice on launch when a newer version is on GitHub. It only tells you: the app does not update itself.
  • Lila Light and Lila Dark themes, and a theme that follows the system's light/dark setting.
• Engine and CLI: published on npm as @lila-modeler/engine (under the beta tag), with lila --version and a CLI reference written for agents (docs/CLI.md).

Install on macOS (Apple Silicon)

Download Lila-Modeler-1.0.0-beta.18-mac-arm64.dmg, open it and drag the app to Applications. The app is ad-hoc sealed but not notarized, so macOS blocks the first launch: double-click the app once, then go to System Settings ▸ Privacy & Security and click Open Anyway next to the message naming Lila Modeler, and confirm Open. On older macOS, Control-click the app ▸ Open ▸ Open works directly. Do not disable Gatekeeper. Full walkthrough: desktop beta guide.

Install on Windows (x64) — help us test it

Download Lila-Modeler-1.0.0-beta.18-win-x64.exe and double-click it. The installer is not signed and has not been tested on a real Windows machine yet, so expect rough edges. Windows SmartScreen will show “Windows protected your PC”: click More info, then Run anyway.

If you can spare 30 minutes, the Windows tester guide walks you through installing, opening an example, simulating, exporting to Excel and Word, importing from Excel and saving a .lila, and ends with a template to report what worked and what failed (open an issue or send it to us).

Verify the download

Put the installer and SHA256SUMS in the same folder. On macOS:

shasum -a 256 -c --ignore-missing SHA256SUMS

--ignore-missing skips the installer you did not download (SHA256SUMS lists both). On Windows, open PowerShell in the folder with the file (File Explorer ▸ right-click ▸ Open in Terminal) and compare the output of the following with the line for the .exe in SHA256SUMS; upper and lower case do not matter:

Get-FileHash .\Lila-Modeler-1.0.0-beta.18-win-x64.exe -Algorithm SHA256

Known limitations

• Windows: the installer is unsigned and untested on a real Windows machine. There is no promise of a signed Windows build.
• macOS: not notarized (Open Anyway on first launch); tested on macOS 27.0, Apple Silicon only. No Intel build.
• Linux: CI builds an AppImage, but it is untested and not attached to this release.
• Web: Chrome is the browser that was tested; Safari acceptance is pending (#379).
• No automatic updates: the desktop app tells you when a newer version is on GitHub and opens its release page, but nothing is installed in place.
• Projects with several processes cannot be opened by beta.14 or earlier; one-process projects still save in the older layout.