Desktop Install

Choose the install path that fits the user

There are really two tracks:

1. Normal users should get a familiar installer they can double-click.
2. Technical users should also have Homebrew, Scoop, and shell installs ready.

The important rule is that the desktop app and the logos CLI should install together instead of feeling like two separate products.

Native installers

macOS

Use the .pkg installer from the public GitHub releases page. That is the right fit when you want one familiar file that can:

• place Logos AI.app in /Applications
• install a logos-ai launcher on PATH
• install the bundled logos CLI on PATH
• feel normal to people who do not want to touch a terminal

Why not .dmg only? Because a drag-and-drop app image is fine for app-only delivery, but it is not the normal answer when you also want to install a CLI.

Windows

Use the .exe installer from the public GitHub releases page. That gives non-technical Windows users a standard install flow while still shipping the desktop app and the CLI together.

Scoop is still worth keeping for technical users, but the .exe is the main on-ramp for normal desktop installs.

Linux

Use the .deb package for Ubuntu-class systems when you want the most normal desktop install. Keep the AppImage and shell bundle around for users who need a lighter or less opinionated path.

The Linux packaging direction is:

• .deb for the normal desktop path
• AppImage for a portable GUI build
• install.sh for a CLI-friendly bundle install

Package managers and shell installs

These are the power-user paths. Keep them documented even if the native installers do most of the work:

# Homebrew cask
brew tap jd4rider/logos-ai https://github.com/jd4rider/homebrew-logos-ai
brew install --cask logos-ai

# Scoop
scoop bucket add logos-ai https://github.com/jd4rider/scoop-logos-ai
scoop install logos-ai

# macOS / Linux shell bundle
curl -fsSL https://raw.githubusercontent.com/jd4rider/logos-releases/main/install.sh | bash

On macOS, the .pkg installer places the app in /Applications. The shell installer uses ~/Applications/logos-ai.app by default. Both also install a logos-ai launcher plus the logos CLI into PATH. The public release assets live at https://github.com/jd4rider/logos-releases/releases.

Optional setup help

If you want a done-for-you environment, setup help can be offered as a paid convenience layer.

That can cover:

• Ollama installation
• Kokoro or Piper voice setup
• guided API.Bible key setup

The likely long-term direction is a premium add-on that automates more of this on supported systems while the free and BYOK paths remain available.

Read-aloud setup

The app can fall back to system speech on macOS, Windows, and Linux, but for the best Bible reading voices you should set up Kokoro or Piper.

• Recommended: Voices and Read-Aloud
• Best quality: Kokoro
• Good alternative: Piper
• Linux fallback: espeak-ng, espeak, or spd-say

What the desktop app adds

The desktop build is where the heavier workflows live:

• offline-friendly reading
• Logos Chat and local AI with Ollama
• read-aloud
• future sermon, export, and study workspace features

The website is intentionally lighter. It gets people into the product fast, then hands them off to the fuller install when they want more depth.