@av-pi-studio/cli 0.0.115 → 0.0.117

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.md CHANGED
@@ -11,7 +11,7 @@ pi-studio ui # serve the browser UI, connected to that daemon
11
11
  ```
12
12
 
13
13
  <p align="center">
14
- <img src="https://cdn.jsdelivr.net/npm/@av-pi-studio/cli@0.0.115/assets/screenshots/chat-workspace.webp" alt="Pi-Studio web UI — an agent reading, editing, and running shell commands, each as its own tool-call card" width="850">
14
+ <img src="https://cdn.jsdelivr.net/npm/@av-pi-studio/cli@0.0.117/assets/screenshots/chat-workspace.webp" alt="Pi-Studio web UI — an agent reading, editing, and running shell commands, each as its own tool-call card" width="850">
15
15
  </p>
16
16
 
17
17
  ---
@@ -68,20 +68,20 @@ own card, with live diff stats, right in the chat.
68
68
  Review what it changed without leaving the tab — a full diff view, line by line:
69
69
 
70
70
  <p align="center">
71
- <img src="https://cdn.jsdelivr.net/npm/@av-pi-studio/cli@0.0.115/assets/screenshots/git-diff.webp" alt="Pi-Studio web UI — git changes diff view" width="850">
71
+ <img src="https://cdn.jsdelivr.net/npm/@av-pi-studio/cli@0.0.117/assets/screenshots/git-diff.webp" alt="Pi-Studio web UI — git changes diff view" width="850">
72
72
  </p>
73
73
 
74
74
  Split the workspace into multiple panes — chat next to a live terminal (backed by `node-pty`), a
75
75
  file, or another session — and the layout persists across reloads:
76
76
 
77
77
  <p align="center">
78
- <img src="https://cdn.jsdelivr.net/npm/@av-pi-studio/cli@0.0.115/assets/screenshots/split-panes.webp" alt="Pi-Studio web UI — split panes with chat and a live terminal side by side" width="850">
78
+ <img src="https://cdn.jsdelivr.net/npm/@av-pi-studio/cli@0.0.117/assets/screenshots/split-panes.webp" alt="Pi-Studio web UI — split panes with chat and a live terminal side by side" width="850">
79
79
  </p>
80
80
 
81
81
  Every file opens with full syntax highlighting:
82
82
 
83
83
  <p align="center">
84
- <img src="https://cdn.jsdelivr.net/npm/@av-pi-studio/cli@0.0.115/assets/screenshots/code-viewer.webp" alt="Pi-Studio web UI — syntax-highlighted code viewer" width="850">
84
+ <img src="https://cdn.jsdelivr.net/npm/@av-pi-studio/cli@0.0.117/assets/screenshots/code-viewer.webp" alt="Pi-Studio web UI — syntax-highlighted code viewer" width="850">
85
85
  </p>
86
86
 
87
87
  See the [`ui`](#ui) command below for every flag, and
@@ -240,7 +240,7 @@ available without installing anything.
240
240
 
241
241
  ### Feature groups
242
242
 
243
- `chat`, `terminal`, `loop`, `schedule`, `permit`, `provider`, and `worktree` are sibling top-level
243
+ `chat`, `terminal`, `loop`, `schedule`, `provider`, and `worktree` are sibling top-level
244
244
  command groups (there is no `feature` wrapper, and no `project` group — opening a project is the
245
245
  top-level `open <path>` command shown above):
246
246
 
@@ -250,7 +250,6 @@ top-level `open <path>` command shown above):
250
250
  | `terminal` | `ls`, `create [--workspace] [--cwd]`, `capture <slot>`, `send-keys <slot> <data>`, `kill <slot>` |
251
251
  | `loop` | `run <prompt> [--max]`, `ls`, `inspect <loopId>`, `logs <loopId>`, `stop <loopId>` |
252
252
  | `schedule` | `create <cron> <prompt>`, `ls`, `inspect <id>`, `update <id> [--cron] [--prompt]`, `pause <id>`, `resume <id>`, `run-once <id>`, `logs <id>`, `delete <id>` |
253
- | `permit` | `ls`, `allow <permissionRequestId>`, `deny <permissionRequestId>` |
254
253
  | `provider` | `ls`, `models <providerId>` |
255
254
  | `worktree` | `create <name> [--workspace]`, `ls`, `archive <name>` |
256
255
 
package/README.md.orig CHANGED
@@ -240,7 +240,7 @@ available without installing anything.
240
240
 
241
241
  ### Feature groups
242
242
 
243
- `chat`, `terminal`, `loop`, `schedule`, `permit`, `provider`, and `worktree` are sibling top-level
243
+ `chat`, `terminal`, `loop`, `schedule`, `provider`, and `worktree` are sibling top-level
244
244
  command groups (there is no `feature` wrapper, and no `project` group — opening a project is the
245
245
  top-level `open <path>` command shown above):
246
246
 
@@ -250,7 +250,6 @@ top-level `open <path>` command shown above):
250
250
  | `terminal` | `ls`, `create [--workspace] [--cwd]`, `capture <slot>`, `send-keys <slot> <data>`, `kill <slot>` |
251
251
  | `loop` | `run <prompt> [--max]`, `ls`, `inspect <loopId>`, `logs <loopId>`, `stop <loopId>` |
252
252
  | `schedule` | `create <cron> <prompt>`, `ls`, `inspect <id>`, `update <id> [--cron] [--prompt]`, `pause <id>`, `resume <id>`, `run-once <id>`, `logs <id>`, `delete <id>` |
253
- | `permit` | `ls`, `allow <permissionRequestId>`, `deny <permissionRequestId>` |
254
253
  | `provider` | `ls`, `models <providerId>` |
255
254
  | `worktree` | `create <name> [--workspace]`, `ls`, `archive <name>` |
256
255
 
@@ -1,11 +1,11 @@
1
1
  import type { Command } from "commander";
2
2
  import { type CliContext, type GlobalOptions } from "./cli-core.js";
3
3
  /**
4
- * Feature command groups (features/cli.md § Command tree): chat, terminal, loop, schedule, permit,
5
- * provider, worktree, plus top-level `open`/`<path>`. Each command maps to the same WS RPC as its
6
- * app/MCP equivalent.
4
+ * Feature command groups (features/cli.md § Command tree): chat, terminal, loop, schedule, provider,
5
+ * worktree, plus top-level `open`/`<path>`. Each command maps to the same WS RPC as its app/MCP
6
+ * equivalent.
7
7
  *
8
- * Terminal / worktree / provider / permission RPC names match registered daemon handlers and MCP
8
+ * Terminal / worktree / provider RPC names match registered daemon handlers and MCP
9
9
  * tools. Chat / loop / schedule wire names follow the daemon's `_request` convention and the message
10
10
  * names in the per-feature scopes (e.g. `ChatCreateRequest` → `chat_create_request`); their daemon
11
11
  * handlers land in an integration sprint — flagged TODO(verify) in `FEATURE_RPC`.
@@ -37,8 +37,6 @@ export declare const FEATURE_RPC: {
37
37
  readonly scheduleRunOnce: "schedule_run_once_request";
38
38
  readonly scheduleLogs: "schedule_logs_request";
39
39
  readonly scheduleDelete: "schedule_delete_request";
40
- readonly permitRespond: "respond_to_permission";
41
- readonly permitList: "list_permissions_request";
42
40
  readonly providerList: "list_providers";
43
41
  readonly providerModels: "list_models";
44
42
  readonly worktreeCreate: "create_pistudio_worktree_request";
@@ -1,11 +1,11 @@
1
1
  import { EXIT_OK, withDaemon } from "./cli-core.js";
2
2
  import { renderJson, renderObject, renderTable } from "./output.js";
3
3
  /**
4
- * Feature command groups (features/cli.md § Command tree): chat, terminal, loop, schedule, permit,
5
- * provider, worktree, plus top-level `open`/`<path>`. Each command maps to the same WS RPC as its
6
- * app/MCP equivalent.
4
+ * Feature command groups (features/cli.md § Command tree): chat, terminal, loop, schedule, provider,
5
+ * worktree, plus top-level `open`/`<path>`. Each command maps to the same WS RPC as its app/MCP
6
+ * equivalent.
7
7
  *
8
- * Terminal / worktree / provider / permission RPC names match registered daemon handlers and MCP
8
+ * Terminal / worktree / provider RPC names match registered daemon handlers and MCP
9
9
  * tools. Chat / loop / schedule wire names follow the daemon's `_request` convention and the message
10
10
  * names in the per-feature scopes (e.g. `ChatCreateRequest` → `chat_create_request`); their daemon
11
11
  * handlers land in an integration sprint — flagged TODO(verify) in `FEATURE_RPC`.
@@ -41,9 +41,6 @@ export const FEATURE_RPC = {
41
41
  scheduleRunOnce: "schedule_run_once_request",
42
42
  scheduleLogs: "schedule_logs_request",
43
43
  scheduleDelete: "schedule_delete_request",
44
- // permit (registered: respond_to_permission alias). list — TODO(verify).
45
- permitRespond: "respond_to_permission",
46
- permitList: "list_permissions_request",
47
44
  // provider (MCP tools / facade RPCs).
48
45
  providerList: "list_providers",
49
46
  providerModels: "list_models",
@@ -198,20 +195,6 @@ export function registerFeatureCommands(program, ctx, setExit) {
198
195
  .command("delete <id>")
199
196
  .description("delete a schedule")
200
197
  .action((id) => run(FEATURE_RPC.scheduleDelete, { scheduleId: id }, ack("deleted")));
201
- // ── permit ──
202
- const permit = program.command("permit").description("tool-call permissions");
203
- permit
204
- .command("ls")
205
- .description("list pending permission requests")
206
- .action(() => run(FEATURE_RPC.permitList, {}, tableOf("permissions", ["permissionRequestId", "tool", "agentId"])));
207
- permit
208
- .command("allow <permissionRequestId>")
209
- .description("allow a pending permission")
210
- .action((id) => run(FEATURE_RPC.permitRespond, { permissionRequestId: id, response: "allow" }, ack("allowed")));
211
- permit
212
- .command("deny <permissionRequestId>")
213
- .description("deny a pending permission")
214
- .action((id) => run(FEATURE_RPC.permitRespond, { permissionRequestId: id, response: "deny" }, ack("denied")));
215
198
  // ── provider ──
216
199
  const provider = program.command("provider").description("agent providers");
217
200
  provider
package/dist/pairing.d.ts CHANGED
@@ -13,7 +13,7 @@
13
13
  */
14
14
  /**
15
15
  * Default pairing-link origin — Pi-Studio's own production web-client (deployed to Dokploy's
16
- * `molagent-platform` project; `docker/README.md` § Deploying to production). Override via
16
+ * `molagent` project; `docker/README.md` § Deploying to production). Override via
17
17
  * `PI_STUDIO_APP_BASE_URL` (`config.app.baseUrl`) for self-hosted/local deployments, e.g.
18
18
  * `http://localhost:8080` — see `daemon-commands.ts`'s `resolvePairingRelayInfo`/`printPairing`.
19
19
  */
package/dist/pairing.js CHANGED
@@ -15,7 +15,7 @@ import { join } from "node:path";
15
15
  */
16
16
  /**
17
17
  * Default pairing-link origin — Pi-Studio's own production web-client (deployed to Dokploy's
18
- * `molagent-platform` project; `docker/README.md` § Deploying to production). Override via
18
+ * `molagent` project; `docker/README.md` § Deploying to production). Override via
19
19
  * `PI_STUDIO_APP_BASE_URL` (`config.app.baseUrl`) for self-hosted/local deployments, e.g.
20
20
  * `http://localhost:8080` — see `daemon-commands.ts`'s `resolvePairingRelayInfo`/`printPairing`.
21
21
  */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@av-pi-studio/cli",
3
- "version": "0.0.115",
3
+ "version": "0.0.117",
4
4
  "repository": {
5
5
  "type": "git",
6
6
  "url": "git+https://github.com/avatsaev/pi-studio.git",
@@ -29,11 +29,11 @@
29
29
  "clean": "rm -rf dist *.tsbuildinfo"
30
30
  },
31
31
  "dependencies": {
32
- "@av-pi-studio/client": "^0.0.115",
33
- "@av-pi-studio/protocol": "^0.0.115",
34
- "@av-pi-studio/relay": "^0.0.115",
35
- "@av-pi-studio/server": "^0.0.115",
36
- "@av-pi-studio/web-client": "^0.0.115",
32
+ "@av-pi-studio/client": "^0.0.117",
33
+ "@av-pi-studio/protocol": "^0.0.117",
34
+ "@av-pi-studio/relay": "^0.0.117",
35
+ "@av-pi-studio/server": "^0.0.117",
36
+ "@av-pi-studio/web-client": "^0.0.117",
37
37
  "@earendil-works/pi-coding-agent": "^1.4.0",
38
38
  "@inquirer/prompts": "^8.5.2",
39
39
  "bcryptjs": "^3.0.3",