pi-t3-bridge 0.7.1 → 0.7.2

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Change log
 
+## 0.7.2, 5 November 2026
+
+Version 0.7.2 stops pi-amplike's permission prompt in T3 threads. T3 has its own permission system, so the bridge no longer loads amplike's `permissions` extension inside T3, and Pi no longer asks "Permission required ... Allow?" before bash commands there. Outside T3, amplike's `/permissions` and its prompts work as before.
+
 ## 0.7.1, 4 November 2026
 
 Version 0.7.1 changes only the documentation. The README now covers all four extensions and the pi-amplike adapter, and the package now ships this change log.

package/README.md

@@ -289,8 +289,9 @@ In a T3 thread, the adapter changes the following parts of amplike:
 | `handoff` tool and `/handoff <goal>` | Writes a summary with the session model, then starts a new T3 thread. The current thread keeps its own session file. |
 | `/mode` | Works as in the terminal, and sends each model and thinking change to T3, so T3's model picker shows the same model. |
 | Shortcuts | The adapter turns them off, because T3 sends Pi no key presses. |
+| `/permissions` and its bash prompts | The adapter doesn't load them, because T3 has its own permission system and amplike's prompt would ask a second time. |
 
-`session_query`, `/permissions`, and amplike's skills work unchanged. The diagram below shows the three commands that talk to T3.
+`session_query` and amplike's skills work unchanged. The diagram below shows the three commands that talk to T3.
 
 ```mermaid
 sequenceDiagram

package/amplike.ts

@@ -1,3 +1,5 @@
+import path from "node:path";
+
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
 
 import {
@@ -8,6 +10,10 @@ import {
 import { t3View } from "./src/amplike/t3-view.ts";
 import { insideT3 } from "./src/bridge/t3-http.ts";
 
+// T3 asks the user before risky tool calls itself, so amplike's bash prompt
+// would ask a second time.
+const T3_SKIPPED_EXTENSIONS: ReadonlySet<string> = new Set(["permissions"]);
+
 // Loads pi-amplike's extensions in place of Pi, so a T3 thread gets T3's
 // versions of the parts T3 can't show. Outside T3 amplike loads unchanged.
 // It runs only when the settings entry for amplike turns its extensions off.
@@ -33,11 +39,17 @@ const amplikeExtension = async (pi: ExtensionAPI): Promise<void> => {
     return;
   }
 
-  const host = insideT3()
-    ? t3View(pi, await loadModeSpecFrom(amplike.root))
-    : pi;
+  const inT3 = insideT3();
+
+  const host = inT3 ? t3View(pi, await loadModeSpecFrom(amplike.root)) : pi;
+
+  const files = inT3
+    ? amplike.extensions.filter(
+        (file) => !T3_SKIPPED_EXTENSIONS.has(path.parse(file).name)
+      )
+    : amplike.extensions;
 
-  const factories = await Promise.all(amplike.extensions.map(loadFactory));
+  const factories = await Promise.all(files.map(loadFactory));
 
   // Each call starts in file order, as when Pi loads the files itself.
   await Promise.all(factories.map((factory) => factory(host)));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-t3-bridge",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "description": "Pi extension adapter for t3-pstack inside T3 Code.",
   "keywords": [
     "pi-extension",