@pipod/cli 0.1.8 → 0.1.10

package/docs/config-simplification.md

@@ -18,7 +18,7 @@
 Retired config keys fail closed in `validateConfig` (and in `planAccountLaunch`
 before resolve — covering nested `pi.hostConfig` lists and the machine layer
 `~/.pi-pod/config.json`, whose only ever-read keys are the template pin,
-`secretResolver`, and `pi.chords`/`pi.sessionNaming`) because silently ignoring a
+`secretResolver`, and `pi.chords`/`pi.sessionNaming`/`pi.podExtensions`) because silently ignoring a
 custom script path would read the wrong file. Server-resident bundles carrying
 retired keys (old templates) are stripped with a warning on pull and
 launch-preview — `push` clears them; `diff` strips silently by design (it is
@@ -33,7 +33,7 @@ One deep boundary, `stripNonBundleKeys` (`toOutgoingBundleConfig` for raw files)
 drops everything a bundle payload must not contain: the rejected keys
 (`template` — the local pin, a template id travels instead; `reuse`;
 `envFile`/`initScript`/`bakeScript`; `pi.hostConfig.skills`/`extensions`) plus
-client-only metadata (`$schema`, `secretResolver`, `pi.chords`/`pi.sessionNaming`).
+client-only metadata (`$schema`, `secretResolver`, `pi.chords`/`pi.sessionNaming`/`pi.podExtensions`).
 Covered paths: project/user/org-dir compilation, the launch bootstrap preview,
 `templates create/edit --config`, and `settings user|org edit|set` — the settings
 verbs validate the edited config locally first (types and retired keys fail
@@ -58,6 +58,7 @@ explicit `set reuse true` fails visibly rather than vanishing.
   server-side; `packages` is enforced on both sides (local sanitize/filter plus
   the server install gate).
 - `pi.chords` / `pi.sessionNaming` — client-only UI preferences, stripped before anything travels.
+- `pi.podExtensions` — client-only: whether a pod's attested Pi extensions run on this machine without asking (`"ask"` or `"run"`). Read only from `~/.pi-pod/config.json`, so no server layer can choose to run code on someone's machine.
 - `secretResolver` / `$schema` — client-only op:// resolution config / schema hint; never travel.
 
 ## Retained: CLI surface (complete inventory)

package/man/pipod-config.5

@@ -1,4 +1,4 @@
-.TH "PIPOD\-CONFIG" "5" "October 2026" "0.1.8"
+.TH "PIPOD\-CONFIG" "5" "October 2026" "0.1.10"
 .SH "NAME"
 \fBpipod-config\fR \- pi pod configuration files
 .SH SYNOPSIS
@@ -94,6 +94,10 @@ pi\.chords                keystrokes for /pod commands while attached:
                            "bindings": { "d": "detach", "a": "archive", "s": "status",
                                          "l": "list", "w": "switch" } }
 pi\.sessionNaming         "auto" (default) names a session from its first prompt; "off"
+pi\.podExtensions         a pod's Pi extensions run on this machine, as you, to render in
+                         the terminal: "ask" (default) confirms each new extension
+                         version; "run" runs them without asking (read only from
+                         ~/\.pi\-pod/config\.json)
 $schema                  ignored
 .fi
 .RE

package/man/pipod-config.5.md

@@ -91,6 +91,10 @@ pi.chords                keystrokes for /pod commands while attached:
                            "bindings": { "d": "detach", "a": "archive", "s": "status",
                                          "l": "list", "w": "switch" } }
 pi.sessionNaming         "auto" (default) names a session from its first prompt; "off"
+pi.podExtensions         a pod's Pi extensions run on this machine, as you, to render in
+                         the terminal: "ask" (default) confirms each new extension
+                         version; "run" runs them without asking (read only from
+                         ~/.pi-pod/config.json)
 $schema                  ignored
 ```
 

package/man/pipod.1

@@ -1,4 +1,4 @@
-.TH "PIPOD" "1" "October 2026" "0.1.8"
+.TH "PIPOD" "1" "October 2026" "0.1.10"
 .SH "NAME"
 \fBpipod\fR \- run pi coding\-agent sessions in server\-managed pods
 .SH SYNOPSIS
@@ -501,7 +501,7 @@ precedes the confirmation; nothing is written when the two already match\.
 
 What pull keeps from the local files:
   config\.json    client\-only keys: $schema, template, secretResolver,
-                 pi\.chords, pi\.sessionNaming
+                 pi\.chords, pi\.sessionNaming, pi\.podExtensions
   settings\.json  hooks and mcpServers (and packages when hostConfig\.packages
                  is off)
   models\.json    credential values the push had dropped

package/man/pipod.1.md

@@ -493,7 +493,7 @@ precedes the confirmation; nothing is written when the two already match.
 
 What pull keeps from the local files:
   config.json    client-only keys: $schema, template, secretResolver,
-                 pi.chords, pi.sessionNaming
+                 pi.chords, pi.sessionNaming, pi.podExtensions
   settings.json  hooks and mcpServers (and packages when hostConfig.packages
                  is off)
   models.json    credential values the push had dropped

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pipod/cli",
-  "version": "0.1.8",
+  "version": "0.1.10",
   "description": "Run pi coding-agent sessions in server-managed pods",
   "type": "module",
   "license": "AGPL-3.0-only",

package/templates/user-config.jsonc

@@ -20,6 +20,10 @@
         "w": "switch"
       }
     },
-    "sessionNaming": "auto"
+    "sessionNaming": "auto",
+
+    // A pod's Pi extensions run on this machine, as you, to render in your terminal. "ask"
+    // confirms each new extension version; "run" runs them all without asking.
+    "podExtensions": "ask"
   }
 }