Repository navigation
Description
Why
Today the only way to run ai-buddy is cargo run from a checkout. A new user who likes the README should be able to download a build. #199 and #200 will own autostart and auto-update once there is a binary to install and a channel to update from. This issue is the binary and the channel, not the tray.
Scope
First-class macOS and Linux packages. Windows stays out of v1 (SPEC: Windows is stubbed; the platform interface exists).
macOS is the real overlay (click-through, Perches, capture exclusion). Linux is a supported degraded Spatial Layer (screen-edge physics, no window geometry under Wayland). A Linux package is still worth shipping so people can try the Engine and the sprite; the README should say what they will and will not get.
In
- Tauri bundle targets beyond the current
app-only config (src-tauri/tauri.conf.json). - macOS: a signed-enough
.app/.dmg(or.appin a zip) that a non-developer can open. Notarization and Developer ID can land in a follow-up if they block the first drop. - Linux: at least one installable artifact people actually use (AppImage and/or
.deb). Wayland/X11 notes belong in the README, not as a reason to skip the package. - CI that builds those artifacts on tag (or on a release workflow). Artifacts attached to a GitHub Release.
- A short install path the README can point at, replacing "clone and cargo run" as the default for new users.
cargo runstays for contributors.
Out
- Windows packages.
- Tray and settings (Tray and settings #18). Launch at login (Launch at login #199). In-app updater (Auto-update #200).
- Homebrew / Flathub / AUR the first time out unless they are cheap once CI exists. Mention them as follow-ups, do not block the first Release on them.
- Changing overlay behavior on Linux. Packaging the degraded mode is enough.
Acceptance
- A GitHub Release contains a macOS build and a Linux build.
- A person without a Rust toolchain can install and launch on each.
- README install instructions use those artifacts, with
cargo rununder Developing. - Linux README copy says the Spatial Layer is degraded (no window Perches).
- This issue does not close Launch at login #199 or Auto-update #200.
Notes
bundle.active is already true; targets is ["app"]. Characters are already bundled via resources. Identifier is dev.omesser.ai-buddy.
Activity
omesser commentedon Sep 2, 2026
Status from #190
Tray/settings UI for Launch at login and the updater shipped as frozen/listed rows only. #190 does not enable either; both stay on Tauri plugins until this issue produces a signed app bundle and a release channel.
No change to this issue’s scope (binary + channel). Autostart/updater wiring remains blocked on artifacts from here.
omesser commentedon Sep 2, 2026
Launch at login and auto-update are no longer on #18 (closed). They are #199 and #200, still blocked on the bundle and release channel from this issue.