jivamai 0.2.37-dev.c5016d5 → 0.2.38-dev.399c52a

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -6,6 +6,30 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
6
6
 
7
7
  ---
8
8
 
9
+ ## [0.2.38] — 2026-11-11
10
+
11
+ ### Added — Jivam is a desktop app on Ubuntu / Linux
12
+
13
+ `jivam install` now builds an applications-menu entry on Linux (x86_64, glibc; tested on Ubuntu 22.04 and 24.04), the way it builds `Jivam.app` on macOS and the Start menu entry on Windows. Until now Linux only had `jivam serve` in a browser tab.
14
+ - The window is drawn by WebKitGTK through the same pinned `@webviewjs/webview` binary (`linux-x64-gnu`, integrity-pinned like the others). It needs the system libraries `libwebkit2gtk-4.1-0` and `libxdo3`, and Jivam offers to install what is missing right where you are: `jivam install` and `jivam` on a terminal ask "Install them now?" and run the one command through `sudo` (Enter is yes; `sudo` asks for your password); `scripts/install.sh` asks the same; from the applications menu a dialog asks and the desktop's own password prompt (`pkexec`) runs it, and the window then opens without a restart. Nothing is installed without a yes, and Jivam never sees the password. Where it cannot ask (no terminal and no dialog tool, `pkexec` missing, an unknown distribution) it prints the `apt` / `dnf` command and opens in the browser.
15
+ - A Jivam that fell back to a browser window is replaced by the native window on the next launch once the cause is fixed, so there is no need to quit it or re-run `jivam install` (also on Windows after WebView2 is installed).
16
+ - `jivam install` no longer ends with "All set." when the window will not open.
17
+ - The menu entry is `~/.local/share/applications/jivam.desktop` with icons in the user's icon theme and a launcher script under `~/.local/share/jivam`. The launcher starts Jivam as `exec -a jivam`, so the window is named `jivam` (X11 `WM_CLASS`, Wayland `app_id`) and the entry can claim it; as plain `node` the dock would show a generic icon. Measured on Ubuntu runners; **not yet seen on a real GNOME or KDE dock.**
18
+ - Starting the window with no graphical session aborts the process (the binary panics in GTK init). A preflight now checks for a display and the libraries, and starts GTK once in a throwaway process, before any window is opened; on a failure Jivam opens in the browser and says why.
19
+ - `jivam uninstall` removes the entry, icons and launcher. It never touches a `jivam.desktop` it did not make.
20
+ - Other architectures, musl (Alpine) and distributions without the libraries keep the browser window.
21
+
22
+ ### Fixed — Linux
23
+ - The filesystem tool's default root was `/Users` (macOS) on every non-Windows system; on Linux it is now `/home`.
24
+ - "Show in folder" after an export did nothing on Linux (opens the folder with `xdg-open`).
25
+ - A launch from the applications menu has no `$SHELL` in some sessions; the PATH lookup now defaults to bash on Linux, not zsh.
26
+ - Start-up errors can now be shown without a terminal (`zenity`, else `notify-send`).
27
+ - An update that fails because Node.js is installed system-wide (npm: permission denied) now says what to do instead of "exited with code 243".
28
+
29
+ ### Changed
30
+ - CI: Ubuntu 22.04 and 24.04 run the real `install`, `check` and `uninstall` under Xvfb, with the WebKitGTK libraries installed. The installers on the website are copied from `scripts/` by `scripts/sync-website-installers.js`.
31
+ - `scripts/install.sh` runs `jivam install` on Linux too, and no longer says "your Mac" there.
32
+
9
33
  ## [0.2.37] — 2026-11-10
10
34
 
11
35
  ### Fixed — Code mode: messages sent after opening an earlier conversation went nowhere
package/README.md CHANGED
@@ -1,8 +1,8 @@
1
1
  # Jivam
2
2
 
3
- Jivam is the desktop UI for [Jiva](https://github.com/KarmaloopAI/Jiva), the autonomous AI agent. It is a small local server (listening on `127.0.0.1` only) shown in a **native window drawn by your operating system's own web view** — WebKit on macOS, Microsoft Edge WebView2 on Windows — installed from npm. No Electron, no code signing, no app store, and no background service.
3
+ Jivam is the desktop UI for [Jiva](https://github.com/KarmaloopAI/Jiva), the autonomous AI agent. It is a small local server (listening on `127.0.0.1` only) shown in a **native window drawn by your operating system's own web view** — WebKit on macOS, Microsoft Edge WebView2 on Windows, WebKitGTK on Linux — installed from npm. No Electron, no code signing, no app store, and no background service.
4
4
 
5
- `jivam install` builds the app on your own machine: `Jivam.app` in your Applications folder on macOS, a Start menu entry on Windows. Nothing that your OS would need to trust is downloaded.
5
+ `jivam install` builds the app on your own machine: `Jivam.app` in your Applications folder on macOS, a Start menu entry on Windows, an applications-menu entry on Linux. Nothing that your OS would need to trust is downloaded.
6
6
 
7
7
  ## Quick Install
8
8
 
@@ -19,8 +19,9 @@ irm https://raw.githubusercontent.com/KarmaloopAI/Jivam/main/scripts/install.ps1
19
19
  The installer will:
20
20
  1. Install Node.js 20+ if not already present (via nvm on Mac/Linux; via winget, or a no-admin portable install if that's not available, on Windows)
21
21
  2. Install `jivamai` and `jiva-core` globally via npm
22
- 3. Run `jivam install`, which adds Jivam to your Applications folder / Start menu, and removes the old background service and Safari / Edge web app if an earlier version left them
23
- 4. Open Jivam — add your model API key and you're ready to go
22
+ 3. On Linux, offer to install the system libraries the window needs if they are missing (for Ubuntu `sudo apt install libwebkit2gtk-4.1-0 libxdo3`; it asks first, Enter is yes, and `sudo` asks for your password)
23
+ 4. Run `jivam install`, which adds Jivam to your Applications folder / Start menu / applications menu, and removes the old background service and Safari / Edge web app if an earlier version left them
24
+ 5. Open Jivam — add your model API key and you're ready to go
24
25
 
25
26
  ## Manual Install
26
27
 
@@ -31,7 +32,7 @@ npm install -g jivamai jiva-core
31
32
  jivam install
32
33
  ```
33
34
 
34
- Afterwards, open Jivam from Applications, Spotlight or the Start menu — or just run `jivam`.
35
+ Afterwards, open Jivam from Applications, Spotlight, the Start menu or your applications menu — or just run `jivam`. On Linux the window needs WebKitGTK 4.1 and libxdo (`sudo apt install libwebkit2gtk-4.1-0 libxdo3` on Ubuntu/Debian, `sudo dnf install webkit2gtk4.1 libxdo` on Fedora); `jivam install` (and `jivam`, and the applications-menu entry) offer to install them if they are missing, and `jivam check` says so.
35
36
 
36
37
  | Command | |
37
38
  |---|---|
@@ -100,7 +101,7 @@ Requires an `NPM_TOKEN` secret set in the repository's GitHub Actions settings.
100
101
  - [jiva-core](https://www.npmjs.com/package/jiva-core) (installed automatically by the install scripts)
101
102
  - macOS 10.15+ (Intel or Apple Silicon) or Windows 10/11 (x64 or ARM64)
102
103
  - Windows 10 may need the Microsoft WebView2 runtime; `jivam install` offers to install it (signed by Microsoft, no administrator rights)
103
- - Linux: no native window yet — use `jivam serve`
104
+ - Linux: x86_64 with glibc, with WebKitGTK 4.1 and libxdo installed (tested on Ubuntu 22.04 and 24.04). On other CPUs, distributions without them, or over SSH Jivam opens in your browser instead: `jivam serve`
104
105
 
105
106
  ## License
106
107