PUBLISHED RELEASE ·

Stable release

Multi Codex v1.5.2

This release corrects Linux AppImage helper discovery when the launcher is opened from another directory. The bundled WebKit helper processes now resolve from the package's own usr/ directory. Packaging also checks that both helpers and the injected bundle are present.

The macOS install and update scripts now use /Applications/Multi Codex.app. Staging and rollback backups stay beside that app. Saved accounts, credentials, conversations and settings keep their existing data locations. Existing apps installed in a different folder are not automatically moved.

The launcher retains quiet update discovery, signed update packages, download progress and restart behavior from v1.5.1. Platform requirements and supported Codex Desktop versions are unchanged. The current Mac release still uses the explicit unsigned-build opt-in described in the installation guide.

Validation

The exact tagged release passed native Linux, Apple Silicon Mac and Windows builds, install/update checks, all four packaged VS Code extension targets, and the Mac account-menu checks. The final Linux AppImage displayed a complete welcome screen in the catalog's offline Firejail sandbox. Direct Linux startup also passed in a disposable runner.

Both Mac scripts were checked for the system /Applications destination and exercised with the real DMG in disposable native fixtures: unsigned-build refusal, explicit opt-in, replacement, signature integrity, startup/restart and preserved account/chat data passed. All 19 downloadable assets match their checksums. The Linux, Mac and Windows update signatures verify against the configured key; altered payloads are rejected.

Native Mac/Windows installers and restart passed; their in-app updater installation paths were not directly rerun for this hotfix. Apple notarization and the wider Linux distribution/desktop matrix remain outside these checks. See the exact package validation report.

The subsequent AppImageHub retry found a remaining helper-library search-path issue on systems without WebKit installed. The native build runner had system WebKit, so its passing launch check did not cover that case. The follow-up fix is published in v1.5.3.