0.6.0

0.6.0 (2026-08-03)

🦙 Hollama Next is now Llooma /ˈluː.mə/

Same app, same llama, its own name. The fork has diverged far enough from Hollama that sharing its name was becoming confusing, for the upstream project as much as for this one.

What changes for you

• The repository is now cedhuf/llooma. GitHub redirects the old URLs, and your existing git remote keeps working.
• The container image moved to ghcr.io/cedhuf/llooma. The old path is no longer published. A registry does not redirect the way a repository does, so an instance still pulling ghcr.io/cedhuf/hollama will simply stop seeing updates quietly, with no error.

Repoint it:

image: ghcr.io/cedhuf/llooma:latest

What you don't have to do, your data migrates itself

• The SQLite database is renamed from hollama.db to llooma.db on first start, -wal and -shm included. Look for Migrated hollama.db to llooma.db in the container logs; it runs once.
• Browser storage keys are carried over on first load.
• Backup files exported before the rename restore exactly as they did before, and always will, an exported file has no way of knowing the app changed its name.

Back up your data directory before updating anyway. The migration is tested, but your database is not the one it was tested on.

Bug Fixes

• jump to the searched message on client-side navigation too (13e684e)
• keep the full-search button in reach whatever the list length (1d81511)

Features

• list the available keyboard shortcuts in settings (40bc84c)
• rename storage keys to Llooma and migrate existing data (8a6b00e)
• rename the app to Llooma (bb5bdbe)