jivamai 0.2.36 → 0.2.37-dev.97cb7bb

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,7 +6,33 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
6
6
 
7
7
  ---
8
8
 
9
- ## [Unreleased]
9
+ ## [0.2.37] — 2026-11-10
10
+
11
+ ### Fixed — Code mode: messages sent after opening an earlier conversation went nowhere
12
+
13
+ - **Fixed** code mode ignoring what you typed after you opened an earlier conversation from the sidebar: the message was not shown and not sent, and when you started a new code session every message you had typed appeared in it and was sent. Opening a conversation set an "initializing" flag that was never cleared, and sending a message waits for that flag. It is now cleared when loading ends, however it ends (success, the pre-0.3.50 fallback, or an error), and likewise when starting a new session fails.
14
+
15
+ ### Fixed — New code session: the Start button could be out of reach
16
+
17
+ - **Fixed** the MCP Servers section opening by default. It stays collapsed (its header still shows how many servers are active).
18
+ - **Fixed** the workspace picker not scrolling. The page clipped anything taller than the window, so with many MCP servers or a short window the Start Code Session button could not be reached. The picker now scrolls.
19
+
20
+ ### Fixed — Conversation menu (⋯): unreadable text
21
+
22
+ - **Fixed** the rename / pin / export / delete menu having a transparent background, so its text overlapped the conversation titles behind it. It now has an opaque background in both themes (new `--menu-bg` token).
23
+ - **Fixed** the hover highlight on those menu items, on the ⋯ button, and on the rename confirm/cancel buttons, which never showed: the colour they used (`--hover-bg`) was not defined anywhere. It is now. The "Clear chat" button in the sidebar used the same colour for its fill, so it now has the light fill its styling asked for instead of none.
24
+
25
+ ### Added — Usage: Synthetic's weekly limit
26
+
27
+ - **Added** the weekly limit to the usage popover for Synthetic, as the share still left ("79.3% left") with its bar and the next regeneration ("+2% in 1h 57m"). Synthetic's `/v2/quotas` reports it as `planWeeklyLimit: { percentRemaining, nextRegenAt, nextRegenPercent }`, with no `limit` or `used`, so Jivam's reader, which only understood count-against-limit windows, skipped it. It now reads that shape too (unit `percent`).
28
+ - The popover already asked Synthetic for fresh numbers every time it opens (one free call, about a second), and still does.
29
+
30
+ ### Changed — Updates: jiva-core is pinned and checked like Jivam itself
31
+
32
+ - **Changed** the in-app update to install `jiva-core` at the exact version that was current when the update was found (`jiva-core@<version>`), as it already did for `jivamai`. A bare `jiva-core` goes through the registry's `latest` tag, which can lag a fresh publish and leave Jivam new and jiva-core old, which loses features such as Synthetic streaming. It is left alone when the machine already has that version or a newer one, so a newer build is not downgraded.
33
+ - **Added** a check after the install that the jiva-core Jivam will load is at least that version. It asks Jivam's own lookup (the global npm root as Jivam's PATH sees it), not the npm that ran the install, because with several Node installs those can be different folders. If they differ, the update stops with a message that names the copy Jivam would still load.
34
+
35
+ ## [0.2.36] — 2026-11-06
10
36
 
11
37
  ### Fixed — Synthetic: long model calls failed with "fetch failed" and the agent kept going
12
38
 
@@ -37,6 +63,8 @@ Jivam is now a "borrowed shell" desktop app. See `docs/architecture/desktop-shel
37
63
  - **Added** tests (`npm test`) and a CI workflow covering Ubuntu, Intel and Apple Silicon macOS, and Windows, on Node 20 and 24.
38
64
 
39
65
 
66
+ ## [Unreleased]
67
+
40
68
  ### Changed — Architecture: Direct SDK Integration
41
69
 
42
70
  After investigation, the Jiva HTTP server (`jiva-core/dist/interfaces/http/index.js`) is designed