DA Vibe Manager 0.1.0b4

The fourth 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.0b4

A round of fixes to the window, from using it: things that got in the way of reading a build,
answering the assistant and changing settings.

• A build's buttons stay in view. A finished build's card is tall (what's new, what was tested,
  the checklist, screenshots), and Install was often out of sight below it. Now Try it
  first, Install and What changed? stay at the bottom of the view while any part of the
  card is on screen, in the chat and in My apps.
• The window opens at the size you left it. It is larger by default (540 × 880), never larger
  than your screen, and remembers the size you resize it to. A backup treats that as this computer's
  own, like where apps are installed.
• What you opened stays open. Expanding the steps list, a step's output, "What it got", "What
  was tested", an app's update schedule or its earlier builds used to collapse again at the next
  word the assistant wrote or the next step of a build. It stays open now.
• The chat stays where you're reading. A settings change or a background refresh no longer
  scrolls the chat to the end; only a new chat does. A settings field you are typing in (your API
  key, a mirror's address) is no longer wiped by a refresh behind it.
• Settings can't put you back on the setup screen. Saving an empty model under "Something else"
  used to throw you onto the first-run screen, and a memory limit that wasn't one (say, "lots")
  stayed in the running settings until it could do harm. A refused setting now changes nothing, and
  the install folder has to be a full path of its own.
• The box to write in asks the right thing. In a chat about improving an app it kept falling
  back to "Ask anything about your computer…" after each keystroke.
• Escape closes any dialog, wherever the focus is. Before, it only worked from a field inside it.
• "Something's wrong" after a try goes to the app's own chat (the one the build came from, or a
  new one about the app), with the panel closed so you can see it, instead of quietly filling the
  box of whatever chat happened to be open. It works from another chat just notes it.
• The window or the browser is a choice in Settings (Settings → This app), from the next
  start. Before, the browser could only be set from the command line.
• New chat from the tray says why when the assistant is busy, rather than doing nothing.
• A Podman command that takes too long can't hang the app any more. If the sandbox took too long
  to start, the app could wait forever on output something it had started still held open, leaving
  the status line on "Starting its sandbox…" for good. It now stops waiting.
• The gateway closes each outgoing connection of the sandbox's fully once it is done.

Install

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

chmod +x DAVibeManager-0.1.0b4-x86_64.AppImage
./DAVibeManager-0.1.0b4-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 an earlier beta: 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; nothing in the
sandbox changed in this release, so it starts as it was.

The README says what it is; the
manual covers the rest.

Verify

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

SHA-256: 61a82802188fdf4d9c4fcc9faa059c6d324b294df29146a43e92432f2a74f30e

The AppImage is reproducible: check out the v0.1.0b4 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.
• Preparing the sandbox depends on Ubuntu's snapshot server, which can be slow: the first
  start can take well over a few minutes when it is. It waits out short outages and says what's
  happening; for longer ones, choose another package source in Settings.
• 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.

DA Vibe Manager 0.1.0b3

The third 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.0b3

• Preparing the sandbox no longer fails when Ubuntu's server has a bad moment. The sandbox's
  packages come from Ubuntu's snapshot server, which is sometimes slow or refuses downloads for a
  while (503 Service Unavailable). The first start used to give up at the first refusal, with an
  error that showed only the end of a long command. Now each step is tried again for about ten
  minutes, keeping what it has already downloaded, so a retry fetches only what's missing. In
  testing, it rode out the server refusing downloads for 13 minutes and started.
• It says what's going on as it happens. While the sandbox is prepared, the status bar, a card
  in the chat and the Sandbox activity panel show how far the downloads are and any trouble, in
  words: which server, what it answered, and when it tries again. If it gives up, it says why in a
  sentence (the server is busy, can't be reached, or its certificate wasn't accepted) and offers
  Try again.
• Another package source, if you want one. Under Settings → The sandbox → If Ubuntu's
  snapshot server is unavailable, choose what happens after those ten minutes: stop and say so
  (the default), use Ubuntu's live archive, or use your own mirror of the Ubuntu archive (https, or
  http on your local network only). apt still checks every package against Ubuntu's signing key,
  but the versions are the current ones, not the pinned ones, and Sandbox activity says so.
• Remove the sandbox, and Podman, from Settings. Settings → The sandbox → Remove the
  sandbox… deletes the sandbox, its files and its images (a few GB), and everything else DA Vibe
  Manager put in Podman, and nothing else of yours there. Do it before uninstalling DA Vibe Manager,
  or to free the space. Tick Also uninstall Podman to remove Podman too, as administrator, with
  the command shown first. If DA Vibe Manager installed Podman, it removes what it installed;
  otherwise just Podman. Your other containers, images and volumes are left alone, and so are your
  apps, chats and backups.
• A build that fails or is stopped cleans up after itself. It used to leave Podman's build
  containers and temporary folders behind, one of them with a 200 MB copy of the Claude Code CLI.
• The Sandbox activity panel no longer shows a stray "null".

Install

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

chmod +x DAVibeManager-0.1.0b3-x86_64.AppImage
./DAVibeManager-0.1.0b3-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.0b2 or 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 first start
after updating prepares the sandbox's image again, which takes a few minutes once. If your sandbox
couldn't start before, it should now.

The README says what it is; the
manual covers the rest,
including when preparing the sandbox takes long or fails
and removing it.

Verify

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

SHA-256: ede6d9b2631baa39c66de8593d1693109058221d4d5dcd55141b7bdef2c6c10c

The AppImage is reproducible: check out the v0.1.0b3 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.
• Preparing the sandbox depends on Ubuntu's snapshot server, which can be slow: the first
  start can take well over a few minutes when it is. It now waits out short outages and says
  what's happening; for longer ones, choose another package source in Settings.
• 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.

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.

DA Vibe Manager v0.1.0b1

The first 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 it does

• Builds the change you want into an app you use. The AI (Claude Code, on a NanoGPT model)
  works in a sealed Podman sandbox: it reads the app's code, makes the change, builds and tests
  it there, and hands you an AppImage to try first and then install, next to your own copy.
• Keeps it up to date. Every app is the project's official release with your changes on top.
  When a new version comes out, your changes are carried over and it's rebuilt by itself, at a
  quiet time you choose; the AI only steps in when a change no longer fits.
• Asks before it touches your computer. The AI can't see your files or run anything here.
  When it needs to look at something, it shows you the exact command and why; nothing runs until
  you click, a second AI reads commands that change things, and you decide what it sees of the
  output, with passwords and keys blanked out.
• What you read is what's built. Each delivery is checked and built from the app's own copy
  of the commit, in a clean container: What changed? is exactly the change in your build.
• Gets apps working here: when an app won't start or misbehaves on your computer, it finds
  out why and fixes the build.
• Shares: a .vibe file of your changes for someone with DA Vibe Manager (their computer
  builds it from the official source, after a reviewer reads the changes), or Export
  AppImage for someone who just wants to run it.
• Backups, locked with your password, to restore on this computer or a new one.

Install

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

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

It needs x86-64 Linux: Ubuntu 24.04 / Mint 22, Debian 13, or a current Fedora, Arch or CachyOS,
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

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.

The README says what it is; the
manual covers the rest.

Verify

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

SHA-256: 793d0998fc9b0f6d822694b2ee39703d81fff48411f3688106b79e1a07075bad

The AppImage is reproducible: check out the v0.1.0b1 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.