Install and update Onevium

Choose an official installer#

Open the Onevium 1.2.1 release and choose an installer under Assets. These are the formats actually published for this version.

Version 1.2.1 has no Linux or Windows arm64 installer. The older 1.1.23 release still provides Linux AppImage and DEB packages for x86_64 and arm64; the historical instructions below do not install 1.2.1. latest*.yml and .blockmap files support the updater; they are not installers.

Check your system and existing work#

• Mac: open Apple menu → About This Mac. Choose arm64 for Apple M-series chips and x64 for Intel.
• Windows: open Settings → System → About and inspect System type. This version's installer targets x64.
• Linux (historical 1.1.23 packages): run uname -m. x86_64 maps to x86_64/amd64; aarch64 or arm64 maps to arm64. On Debian/Ubuntu, dpkg --print-architecture also identifies the DEB architecture.

Before upgrading, save files and finish the current task or record where to resume. An ordinary update does not require deleting app data. See settings and data before making a backup.

Install and launch#

macOS

1. Download the .dmg for your chip and open it.
2. Drag Onevium into Applications. If replacing an existing copy, quit it first and confirm the replacement.
3. Launch Onevium from Applications, not from the mounted disk image. The .zip is an alternative distribution for the same architecture; normally prefer the .dmg.

The 1.2.1 macOS packages use ad-hoc signatures, are not Apple-notarized, and do not use a personal developer certificate. If macOS blocks launch, verify the official download and use its per-app approval flow; do not disable system protection globally.

Windows

Run Onevium-Setup-1.2.1.exe, complete installation, and launch Onevium from the Start menu. This package has no operating-system publisher certificate signature. Save your work before updating rather than continuing in the old window during installation.

Linux: AppImage

These commands are for the historical 1.1.23 packages. Open a terminal in the directory containing the downloaded file. For x86_64:

chmod +x Onevium-1.1.23-x86_64.AppImage
./Onevium-1.1.23-x86_64.AppImage

For arm64:

chmod +x Onevium-1.1.23-arm64.AppImage
./Onevium-1.1.23-arm64.AppImage

AppImage runs directly without a package-manager installation.

Linux: Debian / Ubuntu

For the historical 1.1.23 packages, run the appropriate command in the installer directory:

sudo apt install ./Onevium-1.1.23-amd64.deb

For arm64, replace the filename with Onevium-1.1.23-arm64.deb. Launch Onevium from the application menu afterward.

On first launch, complete the app's account sign-in or license activation. Model access is a separate step; see Connect providers.

Check for and install updates#

Open Settings → General, locate the Onevium version row, and click Check for Updates.

The available action depends on the running environment and update state. Do not infer that updates are always automatic or always manual from the operating system alone.

Moving to 1.2.1

Finish running tasks and quit Onevium before replacing the app. Keep the same OS user and data directory; startup migrates existing conversations and settings automatically. When an existing database needs a schema upgrade, Onevium first creates a consistent local snapshot in upgrade-backups. Do not delete app data to trigger the upgrade.

An older app refuses a newer database schema. Returning to an older app requires the matching pre-upgrade backup; restoring it discards changes made after that snapshot. Keep backups separate from the working data and read settings and data before attempting recovery.

Windows retains its NSIS blockmap differential-update format. Real Windows and Intel Mac installation, and an older-version differential-update flow, have not been exercised on the release build host. Packaging checks and Apple Silicon runtime smoke tests do not replace those installation checks.

Critical application files have integrity signatures. These are separate from macOS notarization or a Windows publisher certificate. To check a downloaded asset, compare its SHA-256 hash with SHA256SUMS from the same official release.

After upgrading, review Settings → Tools if conversation, scheduled-task, or recap tools are missing: these optional tool groups require enablement and do not delete existing data. AI title organization is opt-in. New installations start with browser runtime disabled; existing enabled browser settings are retained.

Verify the running version#

After reopening, check Settings → General for the running version. Open an existing project and conversation to confirm files and history are visible. A working app window does not establish model connectivity; complete the text and tool checks too.

Troubleshoot installation#

Next steps#

Connect a model provider, then follow your first task to open a project and verify the workspace.