Skip to content
OneviumDocs
On this page

Install and update Onevium

Choose the right desktop release, open the app, and verify an update without losing track of your work.

Choose an official installer#

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

System and architecturePackage
Apple silicon MacOnevium-1.3.3-arm64.dmg; a matching .zip is also available
Intel MacOnevium-1.3.3-x64.dmg; a matching .zip is also available
Windows x64Onevium-Setup-1.3.3.exe

Version 1.3.3 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.3.3. 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.

From 1.3.2, the macOS packages are signed with a stable "Onevium" signature. They are not Apple-notarized. 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.3.3.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:

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

For arm64:

bash
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:

bash
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.

What you seeNext action
Download & InstallStart the download and wait for it to finish. Restart when you are ready to end the current work
Restart to UpdateSave your work, restart, then check the version again
Download Manually / View ReleaseOpen the official release, download the correct package, quit the old app, and install the update
An update errorRetain the error details. You can download manually from the official release; an error does not mean the update was installed

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 from 1.3.2 to 1.3.3

Save your work and finish running tasks. Keep the same OS user and data directory. The first launch creates and verifies a main-database snapshot in upgrade-backups, then migrates conversations and settings. Wait for the startup progress to finish; do not force quit or delete app data.

1.3.2 cannot open the upgraded main database. If you must roll back, fully quit Onevium, preserve a separate copy of the current data directory, restore onevium.db from the pre-upgrade snapshot, and move the old onevium.db-wal and onevium.db-shm out of the working directory before starting the older app. Changes made after the snapshot will not be present in that restored main database.

Space stores its own database, resources and versions in the data directory's space folder. The main-database backup does not include all of Space. Before moving machines or rolling back a beta, quit the app and copy the entire data directory; see backup scope.

macOS signing and differential updates

Official 1.3.2 and 1.3.3 macOS packages use the same fixed Onevium signing identity. From 1.3.2, use the in-app update controls. The updater can reuse unchanged blocks when the old package cache and blockmaps are available; download size varies with the release, and it can fall back to a full download.

Older 1.3.1 and ad-hoc beta packages require one manual DMG installation. Quit the app, replace it in Applications, then check system permissions. The fixed signature is not Apple notarization. A new build may ask for keychain access; verify that the request is from Onevium before allowing it.

Changed behavior in 1.3.3

  • Daily Briefing and its dedicated trigger are retired. Install the official Daily review Skill separately for reports and lessons in Space with an optional daily task; old schedules do not migrate automatically. Historical rows remain; ordinary scheduled tasks and memory continue.
  • Review Settings → Permissions and confirmations. With no saved new rule, ordinary confirmations wait 30 seconds then confirm, and questions wait two minutes then use an available default. Required free-text input is never invented. Existing vault timeout-denial settings remain applicable to vault, SSH and sensitive actions.
  • Existing model choices, custom mappings and disabled states are preserved. Restricted catalog models may require manual opt-in after you obtain provider access.
  • Fresh-install defaults do not reset existing personal settings. Review Space before relying on it as your only copy of important files.

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#

SymptomWhat to do
The installer will not runCheck system, architecture, and the complete filename. Do not run .blockmap files or update manifests
AppImage lacks execute permissionRun the chmod +x command above in the file's directory
AppImage reports a missing runtime libraryRecord the named library. On a supported Debian/Ubuntu environment, the matching DEB may be an alternative; dependencies differ between distributions
The old version still appearsConfirm you launched the installed application rather than another copy in Downloads
The system blocks launchVerify the official release source, then use the operating system's per-app approval flow. Do not disable system protection globally
Conversation history is missingCheck the system user and app copy first. Do not overwrite the old data directory with an empty one

Next steps#

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