DA Vibe Manager 0.1.0b2

The second public beta of DA Vibe Manager, a package manager for vibe-coded apps: tell it what
you wish an open-source app could do, and an AI builds you a version that does it. Then it keeps
that app up to date like any other software, carrying your changes over to each new release.

Warning

Beta. Expect rough edges, and use it at your own risk. Read every command it asks to run,
and every change it hands you, before you say yes.

What's new in 0.1.0b2

• Omarchy. DA Vibe Manager now works on Omarchy (Arch with Hyprland).
  Omarchy has no AppImage manager, so apps built here are installed the way Omarchy's own web
  apps are: the AppImage in your apps folder, an entry in the Omarchy menu (Super + Space) and
  its icon in your icon theme. An update replaces it in place. A card at the top of My apps
  offers to put DA Vibe Manager itself in the Omarchy menu, and installs anything Omarchy lacks
  for its window or its apps (a current Omarchy has it all). If you delete an app's entry in the
  Omarchy menu, its card says the app is still installed and offers the entry back.
• The window has its own name on Wayland. Hyprland showed it as __main__.py and couldn't
  match it to its menu entry and icon.
• Looking for new versions is more careful. A look that fails (offline, say) no longer
  forgets what it knew: the release, its change log and whether your changes carried over stay,
  with the error beside them. Before, the next successful look treated the same release as new,
  told you again, and with "straight away" built it again. A look no longer overwrites a skip or
  a build that finished while it was asking, and an app that is being built isn't looked at or
  built a second time.
• A terminal program opens in a terminal window. An app whose menu entry says it runs in a
  terminal (htop, say) used to end at once from Try it first and Open it. It now starts in
  a terminal window, as it does from the menu.
• Going back to an earlier build says why it couldn't, instead of failing with an internal
  error.
• "Build at the quiet time on battery too" now says what it governs: only a build waiting
  for the quiet time. A build you start yourself, or one set to straight away, doesn't wait.
• The one-time move from DA Linux Agent, the app's old name, is gone, and apps made under it
  take DA Vibe Manager's names at their next install instead of a second copy.

Install

Download DAVibeManager-0.1.0b2-x86_64.AppImage, make it executable and run it:

chmod +x DAVibeManager-0.1.0b2-x86_64.AppImage
./DAVibeManager-0.1.0b2-x86_64.AppImage

It needs x86-64 Linux: Ubuntu 24.04 / Mint 22, Debian 13, or a current Fedora, Arch, CachyOS or
Omarchy, with rootless Podman for the sandbox and WebKitGTK for its window:

Distribution
Ubuntu, Mint, Debian	sudo apt install podman gir1.2-webkit2-4.1
Fedora	sudo dnf install podman webkit2gtk4.1
Arch, CachyOS	sudo pacman -S podman passt webkit2gtk-4.1
Omarchy	sudo pacman -S podman passt (it has WebKitGTK)

If Podman is missing, the first screen offers to install it. You need a
NanoGPT API key; it goes to your system keyring and never into the
sandbox. The first start prepares the sandbox, which takes a few minutes and a few GB of disk.

Coming from 0.1.0b1: run the new AppImage in place of the old one (or let Gear Lever or Shelly
replace it). Your settings, apps, chats and sandbox carry on as they are.

The README says what it is; the
manual covers the rest,
with a section on Omarchy.

Verify

sha256sum -c DAVibeManager-0.1.0b2-x86_64.AppImage.sha256

SHA-256: b681b01ee0103eb176c69c4c834f04a5153bf13189ab05c2aa70de32ed272f4e

The AppImage is reproducible: check out the v0.1.0b2 tag and run
packaging/build-appimage.sh build (rootless Podman) to get the same bytes. See
packaging/README.md.

Known limitations

• Building costs money, and nobody can tell how much until the AI has read the app's code:
  on a model paid per use, a few dollars for a simple fix, $50 or more for a big change. Ask it
  how big a change is first, and set a spending limit on your NanoGPT key.
• What you send the assistant could leave your computer. Its sandbox reaches public websites
  (it needs to, to download code and tools), and what a program there sends over HTTPS can't be
  seen from outside. The app keeps your data out of its own web searches, but treat command
  output and attached files you send as shared.
• Changes to the desktop itself (the file manager, the panel) work less well than changes
  to an ordinary app, and need a rebuild with every update. Below the desktop (drivers, system
  services) it doesn't build at all.
• Built apps run on systems as new as Ubuntu 24.04 (the sandbox's base), and newer.
• A shared app's claim to be a newer version can't be verified, so updating from one is
  never chosen for you: take it when you know who sent it.
• The second opinions and the reviewer of shared apps are aids, not guarantees.
• NanoGPT is the only provider set up on the first screen. Linux and x86-64 only, and apps are
  delivered as AppImages, add-ons or source code: no Flatpaks yet.

Feedback

Bugs and ideas: issues. Security
problems: please report privately as described in
SECURITY.md, not in
an issue.

Licensed AGPL-3.0-or-later.