@goodfish/jarvy 0.11.1 → 0.12.1
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 +40 -0
- package/README.md +3 -2
- package/README.zh-CN.md +3 -2
- package/THIRD_PARTY_NOTICE.md +4 -2
- package/dist/server/cli.js +1709 -772
- package/dist/web/assets/data-uMIXh-O1.js +1 -0
- package/dist/web/assets/index-BcZqnyAQ.js +837 -0
- package/dist/web/assets/index-QCSgDIcx.css +1 -0
- package/dist/web/index.html +2 -2
- package/licenses/UNICODE-LICENSE-V3.txt +39 -0
- package/package.json +2 -3
- package/dist/web/assets/figure-DQGUDG-4.js +0 -1
- package/dist/web/assets/index-B20LxZ-9.css +0 -1
- package/dist/web/assets/index-BjM7C3Rt.js +0 -603
- package/dist/web/assets/three.module-BdMZo7zQ.js +0 -4228
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,46 @@
|
|
|
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.12.1 — 2026-11-05
|
|
6
|
+
|
|
7
|
+
No database change: the schema stays v30. Installing now also brings `sharp` with a prebuilt libvips for the platform, about 20 MB.
|
|
8
|
+
|
|
9
|
+
### Changed
|
|
10
|
+
|
|
11
|
+
- **Reactions offer every emoji.** The reaction button opens a panel: a row of answers (👍 👎 👌 ✅ ❌ 👀 🙏 🤔), a search box, and every Unicode 15.1 emoji without skin tones in nine groups, with the last nine you picked on top. Search finds an emoji by its English or Chinese name or keyword: 「OK」 finds 🆗 first, 「收到」 🫡. The list, about 210 KB, loads the first time the panel opens.
|
|
12
|
+
- **A new notice doesn't wake a Bot.** A new version of a channel's notice or a thread's summary no longer wakes an idle Bot or starts a stopped one. A Bot that is working gets it in its current turn; the others see the latest version with their next batch of messages. A Bot still can't post in a chat whose notice it hasn't read, and your sidebar still shows "… updated the notice". On one instance over 30 days, 136 of 211 such deliveries had woken an idle Bot only to read it.
|
|
13
|
+
- **Going back to a chat is instant.** The page remembers the 20 chats and threads you opened last, as you left them: going back to one shows it at once, on the same message at the same height (or at the bottom, with what came meanwhile), without reading anything from the server. Live updates keep them current while they are off screen.
|
|
14
|
+
- **Large pictures get a thumbnail.** A picture's card loads a smaller copy (WebP, inside 1600 × 640), made the first time it is asked for and kept beside the original, so pictures sent before this get one too. The preview and the download still use the original. Ten real screenshots in a channel went from 11.4 MB to 0.67 MB.
|
|
15
|
+
- **Pictures are downloaded once.** The browser keeps an attachment for the session it was fetched with, so switching back to a chat or thread no longer downloads its pictures again. Once you sign out or the session expires, a kept copy isn't used, and signing out also clears them where the browser allows it (HTTPS or this machine).
|
|
16
|
+
- **API**: `GET /api/attachments/:id/thumb` returns a picture's thumbnail, or the original when it gets none. `GET /api/attachments/:id` and `/thumb` answer `Cache-Control: private, max-age=31536000, immutable` with `Vary: Cookie`; `POST /api/logout` answers `Clear-Site-Data: "cache"`.
|
|
17
|
+
|
|
18
|
+
### Fixed
|
|
19
|
+
|
|
20
|
+
- Pictures over 1 MB open in the preview instead of offering only a download. Text, Markdown, HTML and SVG over 1 MB still do, as the page reads them whole.
|
|
21
|
+
- The Bot figure's outline is smooth instead of jagged, and avatars stay sharp after zooming the page or moving the window to another screen.
|
|
22
|
+
|
|
23
|
+
## 0.12.0 — 2026-11-04
|
|
24
|
+
|
|
25
|
+
The database upgrades to v30 on first start (a table for published ports). Sandboxes move to a Docker network of this Jarvy's own the next time they start, keeping what was installed in them.
|
|
26
|
+
|
|
27
|
+
### Added
|
|
28
|
+
|
|
29
|
+
- **Bots publish ports from their sandboxes.** A Bot that runs a web app in its sandbox publishes the port with `ports.publish` and sends you the link. Jarvy serves each published port on a port of its own, taken from a range in Settings → Network (12600–12699 by default), with HTTPS and plain HTTP on the same port and WebSockets passed through; a link keeps working across restarts. Only your signed-in browser and this Jarvy's sandboxes get through, anyone else is asked to sign in, and Jarvy's session cookies never reach the app. Bot info lists the forwarded ports, says whether each app is listening (or only on 127.0.0.1, which can't be forwarded), and can stop forwarding any of them. `ports.list` and `ports.unpublish` go with it.
|
|
30
|
+
- **Sandbox resource limits.** In Bot info, the sandbox's Resource limits row caps its memory (256 MB up to the machine's memory) and CPUs (0.1 up to the machine's count) and shows what it uses now. Nothing is limited by default. A change applies at once, running or stopped, without restarting the sandbox. Over the memory limit only the sandbox's own processes are ended, and a Bot with limits is told them when it lists or switches environments.
|
|
31
|
+
|
|
32
|
+
### Changed
|
|
33
|
+
|
|
34
|
+
- **A new Bot figure.** Bots are drawn as a cat-eared ball by a single shader, in the Bot's colour: the same character from a 22 px avatar to the live figure in a DM. Moods are faces, the figure thinks, reads, works and turns to you, and marks beside its head show sleep, retrying, a pending question or a long turn done. The agent Bot's crown shows from 40 px. Without WebGL a tile in the Bot's colour stands in. three.js is gone, so the page loads about 750 KB less script.
|
|
35
|
+
- **Sandboxes can't reach each other.** A Jarvy's sandboxes share a Docker network of its own with traffic between containers off. They reach this machine (as `host.docker.internal`) and the internet, but not each other or other containers; a published port is how one Bot's service reaches another.
|
|
36
|
+
- **API**:
|
|
37
|
+
- `GET /bots/:id/ports` and `DELETE /bots/:id/ports/:port`; `GET /connection` includes `ports {from, to}`, set with `PUT /connection {ports}`.
|
|
38
|
+
- `PUT /bots/:id/computer/limits {memory, cpus}` (bytes and cores, `null` for none) and `GET /bots/:id/computer/resources`; a sandbox's computer info includes `limits`.
|
|
39
|
+
|
|
40
|
+
### Fixed
|
|
41
|
+
|
|
42
|
+
- Closing one of Jarvy's ports also ends the connections kept open on it (keep-alive and WebSocket), so the port is released at once.
|
|
43
|
+
- A clean `npm ci` of the repository no longer fails on missing `@emnapi/*` packages.
|
|
44
|
+
|
|
5
45
|
## 0.11.1 — 2026-11-03
|
|
6
46
|
|
|
7
47
|
No database change: the schema stays v29.
|
package/README.md
CHANGED
|
@@ -32,9 +32,9 @@ The interface comes in English and Chinese, following your browser's language; s
|
|
|
32
32
|
|
|
33
33
|
**One context per Bot.** A Bot keeps a single session across all its chats, so whatever it learns in one channel it still knows in your DM. Each Bot's own History (what it thought, said and did) can be browsed as an activity timeline, and the Bot can read it back.
|
|
34
34
|
|
|
35
|
-
**Watch it work.** In a DM, the Bot's
|
|
35
|
+
**Watch it work.** In a DM, the Bot's cat acts out its turn as it happens: it thinks, reads, works and turns to you, and a dialogue beside it shows what it is thinking, muttering and sending, and each tool it runs. Click the dialogue to see every step.
|
|
36
36
|
|
|
37
|
-
**Each Bot in its own sandbox.** With Docker installed, a Bot can work in a Linux container only it uses, with Node, Python, git, build tools and Playwright with its browsers, and it can install whatever else it needs. Its workspace is its home there and outlives a reset. Other machines, your computer among them, are added in Settings › Environments and reached over SSH; you choose in Bot info which Bots may switch to each.
|
|
37
|
+
**Each Bot in its own sandbox.** With Docker installed, a Bot can work in a Linux container only it uses, with Node, Python, git, build tools and Playwright with its browsers, and it can install whatever else it needs. Its workspace is its home there and outlives a reset. When it runs a web app there, it publishes the port and sends you a link: Jarvy forwards it to you, signed in, and to your Bots' sandboxes, and to no one else. You can cap each sandbox's memory and CPU in Bot info. Other machines, your computer among them, are added in Settings › Environments and reached over SSH; you choose in Bot info which Bots may switch to each.
|
|
38
38
|
|
|
39
39
|
**An agent Bot that runs Jarvy for you.** Jarvy, the first Bot, wears a crown. Tell it what you want to get done and it builds the team: it creates Bots, writes their personas and picks their models. Later it starts and stops them, checks their usage and clears things away. Anything it deletes waits for your confirmation on a card.
|
|
40
40
|
|
|
@@ -104,6 +104,7 @@ Jarvy is not an internet service.
|
|
|
104
104
|
- It listens on `127.0.0.1` by default. With `--host 0.0.0.0` (or any address other devices can reach) it serves HTTPS with a certificate it makes itself, and sends plain HTTP from other machines to HTTPS. Install that certificate once on each device (Settings → Network), or accept the browser's warning once. Plain HTTP from other machines can be allowed there; the page then warns that passwords, API keys and conversations cross the network unencrypted.
|
|
105
105
|
- Model API keys, secrets (Settings → Secrets) and the certificate keys are encrypted with a master key kept outside the data directory, in `~/.config/jarvy/` (mode `0600`). Back that file up together with the data directory: without it they can't be decrypted. Bots that work on your computer run as your user and could read it; sandboxed Bots can't. The data directory is created with mode `0700` and the database with `0600`.
|
|
106
106
|
- A Bot works in its own sandbox, a Docker container that sees only its workspace and runs with your user and group ids, and on the machines you let it use, where it runs `bash` as the user it logs in as and reaches everything that user can. Being able to use Docker is equivalent to root on this machine.
|
|
107
|
+
- Sandboxes can't reach each other. A port a Bot publishes gets a Jarvy port of its own (Settings → Network, 12600–12699 by default) that only your signed-in browser and this Jarvy's sandboxes get through; Jarvy's session cookies never reach the Bot's app.
|
|
107
108
|
|
|
108
109
|
## License
|
|
109
110
|
|
package/README.zh-CN.md
CHANGED
|
@@ -32,9 +32,9 @@ Jarvy 在本地运行,只有一个用户。账号、Bot、聊天、文件和
|
|
|
32
32
|
|
|
33
33
|
**每个 Bot 一份上下文。** Bot 在所有聊天里用同一个会话,在频道里知道的事,到私信里还记得。每个 Bot 还有自己的 History,记下它想了什么、说了什么、做了什么;你可以按时间线浏览,Bot 自己也能翻看。
|
|
34
34
|
|
|
35
|
-
**看着它干活。** 在私信里,Bot
|
|
35
|
+
**看着它干活。** 在私信里,Bot 的小猫会实时演出它正在做的事:思考、读文件、干活、转过来跟你说话。旁边的对话框显示它在想什么、在自言自语什么、发了什么消息,以及调用的每个工具。点开对话框能看到这一轮的每一步。
|
|
36
36
|
|
|
37
|
-
**每个 Bot 有自己的沙箱。** 装了 Docker,Bot 就可以在只属于它的 Linux 容器里干活,里面有 Node、Python、git、编译工具和带浏览器的 Playwright
|
|
37
|
+
**每个 Bot 有自己的沙箱。** 装了 Docker,Bot 就可以在只属于它的 Linux 容器里干活,里面有 Node、Python、git、编译工具和带浏览器的 Playwright,缺什么它可以自己装。它的工作区就是它在里面的主目录,重置也不会丢。它在沙箱里跑起网页应用后,会发布端口并把链接发给你:Jarvy 只把它转发给已登录的你和各个 Bot 的沙箱。每个沙箱的内存和 CPU 上限都可以在 Bot 信息里设置。其他机器(包括你的电脑)在「设置 › 工作环境」里添加,通过 SSH 连接;哪些 Bot 可以切换过去,在 Bot 信息里设置。
|
|
38
38
|
|
|
39
39
|
**主 Bot 替你打理 Jarvy。** 第一个 Bot Jarvy 戴着皇冠。告诉它你想做什么,它就帮你组好团队:创建 Bot、写好 Persona、选好模型。之后启停 Bot、查用量、清理不用的东西也找它。它要删除任何东西,都会先弹卡片等你确认。
|
|
40
40
|
|
|
@@ -104,6 +104,7 @@ Jarvy 不是面向互联网的服务。
|
|
|
104
104
|
- 默认只监听 `127.0.0.1`。用 `--host 0.0.0.0`(或其他设备能访问到的地址)时,Jarvy 用自己生成的证书提供 HTTPS,其他机器的明文 HTTP 请求会跳转到 HTTPS。在每台设备上装一次这个证书(设置 → 网络),或者在浏览器的警告页上继续访问一次。那里也可以允许其他机器用明文 HTTP 访问,这时页面会提示密码、API Key 和对话内容以明文经过网络。
|
|
105
105
|
- 模型 API Key、密钥(设置 → 密钥)和证书私钥都用主密钥加密,主密钥保存在数据目录之外的 `~/.config/jarvy/`(权限 `0600`)。备份时请把它和数据目录一起保留,否则这些内容无法解密。在你的电脑上工作的 Bot 以你的用户运行,能读到它;沙箱里的 Bot 读不到。数据目录权限是 `0700`,数据库文件是 `0600`。
|
|
106
106
|
- Bot 在自己的沙箱里干活(一个只看得到它工作区的 Docker 容器,用你的用户和组 ID 运行),也可以在你允许的机器上以登录用户的身份运行 `bash`,那个用户能碰到的它都能碰到。能使用 Docker 就等于拥有这台机器的 root 权限。
|
|
107
|
+
- 沙箱之间互相访问不到。Bot 发布的端口由 Jarvy 另开一个端口转发(设置 → 网络,默认 12600–12699),只有已登录的浏览器和本机 Jarvy 的沙箱能访问;Jarvy 的登录 Cookie 不会转给 Bot 的应用。
|
|
107
108
|
|
|
108
109
|
## 许可证
|
|
109
110
|
|
package/THIRD_PARTY_NOTICE.md
CHANGED
|
@@ -4,6 +4,7 @@
|
|
|
4
4
|
|
|
5
5
|
- **shadcn/ui** — `src/web/components/ui/` holds local copies of `badge`, `button`, `card`, `dialog`, `input`, `input-group`, `label`, `scroll-area`, `select` and `textarea` from shadcn/ui (`apps/v4/registry/new-york-v4/ui/`, commit `98a1fe67b439324ddc857f47fbdce056600a4329`), adapted to local imports. © shadcn, MIT; license at `licenses/SHADCN-UI-MIT.txt`.
|
|
6
6
|
- **Bossmode** — `src/web/styles/login.css` adapts the login page layout of Bossmode 0.29.0 (commit `84e742f`, `web/src/styles/login.css`), now on Jarvy's own colours. The attachment preview in `src/web/files/` was reimplemented after Bossmode 0.29.1's file viewer behaviour (static HTML rendering, kinds, navigation). Apache-2.0; license at `licenses/BOSSMODE-APACHE-2.0.txt`.
|
|
7
|
+
- **Unicode emoji data** — `src/web/channel/emoji/data.json` is generated by `scripts/build-emoji.mjs` from Unicode Emoji 15.1's `emoji-test.txt` and the CLDR annotations and derived annotations in English and Chinese (`unicode-org/cldr-json`): the emoji list, its groups, names and keywords. © Unicode, Inc., Unicode License v3; license at `licenses/UNICODE-LICENSE-V3.txt`.
|
|
7
8
|
- **lobe-icons** — `src/web/provider-logos/` holds provider logos copied from `@lobehub/icons-static-svg` 1.95.1 (the colour version where a brand has one), with their size, inline style and title removed. © 2023 LobeHub, MIT; license at `licenses/LOBE-ICONS-MIT.txt`. The logos are the trademarks of their owners and only name the provider.
|
|
8
9
|
|
|
9
10
|
Jarvy's design tokens (`src/web/styles/tokens.css`) and the remaining styles are its own. Icons are [Lucide](https://lucide.dev) (ISC, via `lucide-react`).
|
|
@@ -11,12 +12,13 @@ Jarvy's design tokens (`src/web/styles/tokens.css`) and the remaining styles are
|
|
|
11
12
|
## References
|
|
12
13
|
|
|
13
14
|
- The provider and model settings follow the interaction of **Pi Web** (`agegr/pi-web`, MIT), studied through its frontend source and running UI. Jarvy implements the forms with its own shadcn/Radix controls and does not reuse Pi Web's configuration-file or credential storage.
|
|
14
|
-
- The Bot figure
|
|
15
|
+
- The Bot figure's shader uses distance functions and the smooth minimum described by **Inigo Quilez** (iquilezles.org, MIT).
|
|
15
16
|
|
|
16
17
|
## Dependencies
|
|
17
18
|
|
|
18
19
|
- Runtime: `@earendil-works/pi-coding-agent`, `@earendil-works/pi-ai` and `@earendil-works/pi-env` 1.2.0, `hono` 4.13.11, `@hono/node-server` 2.1.3, `typebox` 1.3.27, `proper-lockfile` 4.1.2, `undici` 8.10.2 — MIT. Jarvy calls Pi's native model, tool, OAuth and refresh APIs rather than copying provider login code.
|
|
19
|
-
-
|
|
20
|
+
- Thumbnails: `sharp` 0.35.5 (© Lovell Fuller and contributors, Apache-2.0). npm installs it with a prebuilt **libvips** for the platform (`@img/sharp-libvips-*`), LGPL-3.0-or-later, loaded as a shared library and unmodified; it can be replaced with another libvips build as sharp's documentation describes. Their licenses ship with the installed packages.
|
|
21
|
+
- Frontend: React, Tailwind CSS, Radix UI, Lucide React, `cn`, class-variance-authority, react-markdown, remark-gfm, remark-breaks — under their own licenses, shipped with the installed packages.
|
|
20
22
|
- Development only: **Agentation** (`agentation` 3.1.2, © Benji Taylor, PolyForm Shield 1.0.0) is loaded only in Vite development builds and is not part of the production build.
|
|
21
23
|
|
|
22
24
|
Jarvy is not affiliated with any of the projects above.
|