@goodfish/jarvy 0.7.0 → 0.9.0

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
@@ -2,6 +2,59 @@
2
2
 
3
3
  All notable changes to Jarvy. Versions follow [semantic versioning](https://semver.org/) as used before 1.0: a patch release only fixes bugs; a minor release adds features or upgrades the database.
4
4
 
5
+ ## 0.9.0 — 2026-10-23
6
+
7
+ Upgrading moves the database from schema v23 to v25 on first start. Each step adds one column and rewrites no rows: `environments.password` holds the sealed password of an SSH machine that refuses keys (v24), and `messages.folded_at` marks a folded message (v25). A v25 database cannot be opened by 0.8.0; keep a copy if you may need to go back.
8
+
9
+ ### Added
10
+
11
+ - **SSH machines with either a password or a key.** A machine that only takes passwords can now be added. Jarvy still installs its key with the password. When the machine refuses keys, the password is kept sealed under the master key and used to log in. In the machine's details you can update the password, or switch to key login once keys are allowed; the saved password is then deleted. A machine that only takes keys can be added without a password: choose Public key, add the line Jarvy shows to `~/.ssh/authorized_keys`, then verify. A Bot's machine request card offers both. Each machine's details show Jarvy's public key with a copy button. Errors now tell a wrong password from a machine that takes no passwords and from a key that wasn't accepted. (A59)
12
+ - **Long and folded messages.** Message text longer than 12 lines shows its start with Show all. Any message can be folded to one line from its hover actions; a folded message shows the start of its text and a quiet "Folded", and the same action unfolds it. Folding stays after a reload and on other devices. It only changes what you see: Bots read the message as before and are not told. (A60)
13
+ - **Dates in chats.** Channels, threads and DMs show a divider for each day: Today, Yesterday, or the date. In DMs, the first bubble of a group shows its time. Hovering any time shows the full date, and a thread's last reply shows the date when it isn't today.
14
+
15
+ ### Changed
16
+
17
+ - **The @ list in a thread puts the people in it first**, under "In this thread": the root's author, whoever replied, and whoever was @-mentioned there. The rest of the channel follows under "Others in the channel".
18
+ - **A Bot can search only its own messages** with `messages.search {mine: true}`, and its prompt now tells it how to recall past work: find its own message, then read the History around that turn.
19
+ - **Less secondary text in the interface.** Subtitles, page descriptions and second lines that repeat what a heading or the layout already says are gone. A second line stays only for warnings, side effects, limits and steps.
20
+
21
+ ### Fixed
22
+
23
+ - The model menu in Bot info scrolls with the mouse wheel and by touch.
24
+
25
+ ### Known limits
26
+
27
+ - On an SSH machine, `write` and `edit` fail for a path that exists on the machine running Jarvy but that Jarvy's user can't read there. `bash` still works there. This waits on a fix in Pi, the agent library Jarvy uses.
28
+
29
+ ## 0.8.0 — 2026-10-22
30
+
31
+ Upgrading moves the database from schema v21 to v23 on first start: the environments table is rebuilt to hold SSH machines, with their sealed keys and host keys (v22), and scheduled tasks get a table of their own while the inbox table is rebuilt with all its rows (v23). A v23 database cannot be opened by 0.7.0; keep a copy if you may need to go back.
32
+
33
+ ### Added
34
+
35
+ - **SSH machines.** Settings › Environments adds a machine reached over SSH: its address, user and an optional start directory. Jarvy first shows the machine's host key fingerprints to check, then you type its password once. Jarvy makes a key for that machine, installs it in `~/.ssh/authorized_keys` and keeps it sealed under the master key; the password is not kept. In Bot info you turn on which Bots may use a machine. A Bot switches there like `cd` when a task needs it, and each batch says where it is. When a Bot needs a machine it doesn't have, it asks on a card in the chat; you check the fingerprints and type the password there. Deleting a machine takes its key back off the machine first. Jarvy checks host keys against its own list and does not read your `~/.ssh/config`. Linux and macOS machines are supported. (A57)
36
+ - **Scheduled tasks.** A Bot can be given work to do later: once at a time, every N minutes (counted from when the task is made), daily or weekly at a time, in this machine's local time. A task has a name, what to do and when. You make, pause, change and delete them in Bot info › Scheduled tasks, and a Bot manages its own with the tasks tools. When a task is due, the Bot gets its instruction in a batch; it never interrupts a turn, and reports to you unless the task says where. Runs missed while Jarvy was not running are skipped, not made up. (A58)
37
+ - **An All range in Bot usage**, beside the shorter ranges.
38
+ - **SHA-1 fingerprint in Settings › Network**, under SHA-256: it is the Thumbprint that Windows' certificate window shows. The install steps end with a reminder to quit the browser completely and open it again.
39
+
40
+ ### Changed
41
+
42
+ - **A changed system prompt is told, not swapped in.** When you change a Bot's persona, name, description, skills or workspace, its running session keeps the prompt the model already has, so the provider's cache of the conversation survives. The change comes with the next batch, once, as a short diff of what changed; the new prompt is taken up when a session starts, after a model switch and after a compaction. (A56)
43
+ - **Chat gateway errors say how to fix the call.** Invalid arguments list what is wrong and include the tool's parameters; an unknown tool name lists the tools there are. A Bot gets a call right on the next try instead of looking the tool up first.
44
+ - **Bot-facing text calls the platform "this chat platform"**, so a Bot doesn't confuse it with the agent Bot, which is named Jarvy by default. The agent Bot is still told the platform's name.
45
+ - **Secrets cover tokens, API keys and passwords**; logging in to a machine goes through the SSH machine card instead.
46
+ - **Composer**: a sent message leaves the input at once, and comes back if sending fails.
47
+ - **Thinking bubble**: keeps following the newest words unless you scroll it up.
48
+
49
+ ### Fixed
50
+
51
+ - A model connection can be deleted once the Bots that used it are deleted. This also clears links that Bots deleted before the upgrade kept. While a Bot still uses a connection, the refusal names it.
52
+
53
+ ### Known limits
54
+
55
+ - On an SSH machine, `write` and `edit` fail for a path that exists on the machine running Jarvy but that Jarvy's user can't read there, such as a protected directory on the same computer. `bash` still works there. This is a limit in Pi, the agent library Jarvy uses, and is waiting on an upstream fix.
56
+ - SSH machines run Bots' commands as the user you gave; there is no sandbox on them.
57
+
5
58
  ## 0.7.0 — 2026-10-21
6
59
 
7
60
  Upgrading moves the database from schema v20 to v21 on first start: secrets, their grants and their uses are added, and the credentials you have already saved are encrypted under a new master key. Keep the master key file if you may need to go back, and keep a copy of the database too: a v21 database cannot be opened by 0.6.0.