@pipod/cli 0.1.7 → 0.1.9

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.
@@ -1,4 +1,4 @@
1
- .TH "PIPOD\-CONFIG" "5" "October 2026" "0.1.7"
1
+ .TH "PIPOD\-CONFIG" "5" "October 2026" "0.1.9"
2
2
  .SH "NAME"
3
3
  \fBpipod-config\fR \- pi pod configuration files
4
4
  .SH SYNOPSIS
package/man/pipod.1 CHANGED
@@ -1,4 +1,4 @@
1
- .TH "PIPOD" "1" "October 2026" "0.1.7"
1
+ .TH "PIPOD" "1" "October 2026" "0.1.9"
2
2
  .SH "NAME"
3
3
  \fBpipod\fR \- run pi coding\-agent sessions in server\-managed pods
4
4
  .SH SYNOPSIS
@@ -269,6 +269,9 @@ the pod's configured Pi resources for that launch; anything else Pi\-related bel
269
269
  \fB\-\-reuse\fP restarts this project's newest stopped pod instead of creating one\. \fB\-\-on <pod>\fP
270
270
  starts the new pod on an existing pod's machine, sharing its files; \fB\-\-on self\fP does that
271
271
  from inside a pod\.
272
+ .P
273
+ Inside a pod, signed in with the pod's own token, every launch (\fB\-\-on self\fP included) and
274
+ every job it schedules uses the template that pod launched from; the server refuses any other\.
272
275
  .SH COMMANDS
273
276
  .SS pipod login
274
277
  .RS 2
@@ -850,7 +853,8 @@ PI_POD_ACCOUNT_URL the server pipod login uses with no \-\-server and no
850
853
  PI_POD_ISSUER the OIDC issuer pipod login uses, for a server too old
851
854
  to publish its own
852
855
  PI_POD_SERVER_URL set in every pod: pipod there signs in with the pod's
853
- PI_POD_SERVER_TOKEN own token, which reaches only the pods it launched
856
+ PI_POD_SERVER_TOKEN own token, which reaches only the pods it launched and
857
+ launches only from the pod's own template
854
858
  VISUAL, EDITOR the editor for pipod settings edit
855
859
  NO_COLOR plain output without color
856
860
  .fi
package/man/pipod.1.md CHANGED
@@ -260,6 +260,9 @@ the pod's configured Pi resources for that launch; anything else Pi-related belo
260
260
  starts the new pod on an existing pod's machine, sharing its files; `--on self` does that
261
261
  from inside a pod.
262
262
 
263
+ Inside a pod, signed in with the pod's own token, every launch (`--on self` included) and
264
+ every job it schedules uses the template that pod launched from; the server refuses any other.
265
+
263
266
  ## COMMANDS
264
267
 
265
268
  ### pipod login
@@ -841,7 +844,8 @@ PI_POD_ACCOUNT_URL the server pipod login uses with no --server and no
841
844
  PI_POD_ISSUER the OIDC issuer pipod login uses, for a server too old
842
845
  to publish its own
843
846
  PI_POD_SERVER_URL set in every pod: pipod there signs in with the pod's
844
- PI_POD_SERVER_TOKEN own token, which reaches only the pods it launched
847
+ PI_POD_SERVER_TOKEN own token, which reaches only the pods it launched and
848
+ launches only from the pod's own template
845
849
  VISUAL, EDITOR the editor for pipod settings edit
846
850
  NO_COLOR plain output without color
847
851
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pipod/cli",
3
- "version": "0.1.7",
3
+ "version": "0.1.9",
4
4
  "description": "Run pi coding-agent sessions in server-managed pods",
5
5
  "type": "module",
6
6
  "license": "AGPL-3.0-only",
@@ -39,8 +39,8 @@
39
39
  "prepublishOnly": "npm run build"
40
40
  },
41
41
  "dependencies": {
42
- "@earendil-works/pi-coding-agent": "0.84.4",
43
- "@earendil-works/pi-tui": "0.84.4",
42
+ "@earendil-works/pi-coding-agent": "1.0.2",
43
+ "@earendil-works/pi-tui": "1.0.2",
44
44
  "cron-parser": "^5.10.0",
45
45
  "jose": "^5.10.0",
46
46
  "ws": "^8.22.0"