pisper 0.0.5 → 0.0.7
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/README.en.md +2 -2
- package/README.md +2 -2
- package/package.json +3 -3
package/README.en.md
CHANGED
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
|
|
9
9
|
<h1 align="center">Pisper</h1>
|
|
10
10
|
|
|
11
|
-
<p align="center"><strong>A
|
|
11
|
+
<p align="center"><strong>A local-first Agent application powered by Pi</strong></p>
|
|
12
12
|
|
|
13
13
|
<p align="center">
|
|
14
14
|
<img src="https://img.shields.io/badge/Node.js-17141F?style=flat-square&logo=nodedotjs&logoColor=F59E0B" alt="Node.js" />
|
|
@@ -151,7 +151,7 @@ npm install -g pisper
|
|
|
151
151
|
pisper
|
|
152
152
|
```
|
|
153
153
|
|
|
154
|
-
After entering the TUI for the first time, use `/
|
|
154
|
+
After entering the TUI for the first time, use `/provider` to choose a Provider and save its API key in a masked input; for a known Provider, `/provider <id>` skips the picker (`/apikey` remains a compatible alias). For visual configuration, run `pisper web`; Pisper installs the signed Web frontend on demand and opens an authenticated, localhost-only settings page in your default browser. **Save Provider settings** does not change the default model; only **Set as default Provider** changes the default for later sessions.
|
|
155
155
|
|
|
156
156
|
After installing the desktop app, you can also install the `pisper` command from **Settings → App updates**. The first installation remains explicit; after later desktop updates restart Pisper, it automatically refreshes this managed terminal client:
|
|
157
157
|
|
package/README.md
CHANGED
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
|
|
9
9
|
<h1 align="center">Pisper</h1>
|
|
10
10
|
|
|
11
|
-
<p align="center"><strong>Pi
|
|
11
|
+
<p align="center"><strong>Pi 驱动的本地 Agent 应用</strong></p>
|
|
12
12
|
|
|
13
13
|
<p align="center">
|
|
14
14
|
<img src="https://img.shields.io/badge/Node.js-17141F?style=flat-square&logo=nodedotjs&logoColor=F59E0B" alt="Node.js" />
|
|
@@ -151,7 +151,7 @@ npm install -g pisper
|
|
|
151
151
|
pisper
|
|
152
152
|
```
|
|
153
153
|
|
|
154
|
-
首次进入 TUI 后使用 `/
|
|
154
|
+
首次进入 TUI 后使用 `/provider` 选择 Provider 并在掩码输入框中保存 API Key；已知 Provider 可用 `/provider <id>` 直达（`/apikey` 为兼容别名）。需要可视化配置时，运行 `pisper web`，Pisper 会按需安装签名 Web 前端并在默认浏览器打开仅监听本机的认证配置页。配置页中的 **保存 Provider 配置** 不会修改默认模型；只有点击 **设为默认 Provider** 才会切换后续会话的默认模型。
|
|
155
155
|
|
|
156
156
|
安装桌面版后，也可以在 **设置 → 应用更新** 中安装 `pisper` 命令。首次安装由你主动确认；之后桌面应用更新并重启时，Pisper 会自动刷新这份已托管的终端客户端：
|
|
157
157
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pisper",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.7",
|
|
4
4
|
"description": "Pisper CLI.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": {
|
|
@@ -40,8 +40,8 @@
|
|
|
40
40
|
},
|
|
41
41
|
"pisper": {
|
|
42
42
|
"repository": "ling-kong-ran/pisper",
|
|
43
|
-
"tuiVersion": "0.4.
|
|
44
|
-
"runtimeVersion": "0.4.
|
|
43
|
+
"tuiVersion": "0.4.33",
|
|
44
|
+
"runtimeVersion": "0.4.35"
|
|
45
45
|
},
|
|
46
46
|
"publishConfig": {
|
|
47
47
|
"access": "public",
|