@herbertgao/pi-extensions 2026.10.2 → 2026.10.4

package/README.md

@@ -21,10 +21,11 @@ When migrating from `pi-mcp-adapter`, remove any standalone adapter install as w
 The package bundles 5 active `@herbertgao/*` child packages—`pi-agency`, `pi-bark`, `pi-cc-extensions`, `pi-subagents`, and `sol-pi`—plus the following upstream packages under their original names:
 
 - `pi-antigravity@0.10.0`
+- `pi-provider-qoder@0.5.0`
 - `@dietrichgebert/ponytail@5.1.0`
 - `@juicesharp/rpiv-ask-user-question@2.12.0`
 - `@narumitw/pi-btw@0.61.1`
-- `@narumitw/pi-caffeinate@0.49.10`
+- `@narumitw/pi-caffeinate@0.49.11`
 - `@pi-plugins/fast-mode@0.1.13`
 - `@tifan/pi-copy-response@0.2.7`
 - `@tifan/pi-handoff@2.2.2`
@@ -37,9 +38,8 @@ The package bundles 5 active `@herbertgao/*` child packages—`pi-agency`, `pi-b
 - `pi-multi-account@1.24.0`
 - `pi-next-cue@1.0.7`
 - `pi-jev-auto-mode@0.5.0`
-- `pi-lens@4.4.0`
-- `pi-web-access@0.37.0`
-- `remote-pi@0.7.0`
+- `pi-lens@4.4.1`
+- `pi-web-access@0.38.0`
 - `resume-from@0.4.1`
 
 Pi loads their extensions and skills through `node_modules/` paths inside one package root. The upstream companions are pinned and bundled, not forked or renamed.
@@ -56,11 +56,11 @@ The locally customized CC and SoL-Pi packages now follow complete upstream basel
 
 `@herbertgao/pi-bark` sends localized Bark pushes when a user-facing Pi run fully settles or `@juicesharp/rpiv-ask-user-question` needs an answer. Notifications include emoji-labeled machine/path metadata and support the bundled official Pi badge through Bark's `icon` parameter. Configure it in `$PI_CODING_AGENT_DIR/bark.json` (normally `~/.pi/agent/bark.json`); see the [package README](../pi-bark/README.md). Without a valid endpoint it stays inactive.
 
-`@narumitw/pi-caffeinate@0.49.10` uses the host platform's sleep inhibitor during each Pi agent run. On macOS, `/caffeinate sleep` keeps the system awake while allowing the display to sleep; `/caffeinate display` also keeps the display awake. It releases the inhibitor when the run or session ends. Its D-Bus dependency remains on the normal socket transport under Node; Bun on Linux/macOS can use FFI and an in-process reader thread for Unix file-descriptor transport, falling back when unavailable. No daemon or build step is added.
+`@narumitw/pi-caffeinate@0.49.11` uses the host platform's sleep inhibitor during each Pi agent run. On macOS, `/caffeinate sleep` keeps the system awake while allowing the display to sleep; `/caffeinate display` also keeps the display awake. It releases the inhibitor when the run or session ends. Its D-Bus dependency remains on the normal socket transport under Node; Bun on Linux/macOS can use FFI and an in-process reader thread for Unix file-descriptor transport, falling back when unavailable. No daemon or build step is added.
 
 `pi-jev-auto-mode@0.5.0` adds fail-closed Jev safety gates for shell commands and file changes. `pi-typesafe@0.9.1` provides `/typesafe` and `typesafe_evaluate` for explicit structured decisions; `/typesafe enable` or `PI_TYPESAFE_ENABLED=1` is still required for agent tool calls. The Pi extension continues to use the TypeSafe API, not Liquid. The package's programmatic client additionally supports Liquid with its own API key and free or paid models; existing usage accounting now merges writes under a short-lived file lock (up to 200ms synchronous wait under contention).
 
-`resume-from@0.4.1` continues sessions across Pi, Claude Code, and Codex; it keeps a Claude Code session matched to its start directory when the active transcript later moves into a nested cwd. `@herbertgao/sol-pi` adds opt-in Action Fusion, ObservationPack, Evidence-Preserving Reducer, and Online Context Compact; see its [configuration guide](../sol-pi/docs/configuration.md). `pi-lens@4.4.0` expands language routing and bounds retained diagnostic facts across multi-root sessions. `pi-web-access@0.37.0` provides configurable web search and fetch tools; its `toolActivation` defaults to `auto`, choosing eager or dynamic tool activation per model. It adds structured search/fetch data for codemode and an optional, manually started `pi-web-access-mcp` stdio CLI; installing the aggregate does not start that server. Degoog and Keenable are explicit-only providers, excluded from automatic and `all` selection. Perplexity search now uses the Search API's ranked pages and snippets rather than a Sonar-generated answer; requests requiring prose still use Sonar. `pi-antigravity@0.10.0` reads Pi 0.86+ transcript system messages, so Antigravity requests carry Pi's system prompt and tools; it also registers `google_search` and `generate_image` tools that use the signed-in Antigravity account. Preferred Thinking 1.0.2 preserves an explicit subagent `--thinking` choice. Deprecated `@tifan/pi-titlebar-spinner` is no longer bundled; Rename remains the single owner of Herdr tab naming.
+`resume-from@0.4.1` continues sessions across Pi, Claude Code, and Codex; it keeps a Claude Code session matched to its start directory when the active transcript later moves into a nested cwd. `@herbertgao/sol-pi` adds opt-in Action Fusion, ObservationPack, Evidence-Preserving Reducer, and Online Context Compact; see its [configuration guide](../sol-pi/docs/configuration.md). `pi-lens@4.4.1` publishes a public LSP config schema, reads user-level custom rule directories (project before user before built-in), normalizes argv-style server entries, downgrades `throw-new-error` to a warning, and counts Docker, JSON, and Jedi servers in idle eviction; language routing and the retained multi-root diagnostic facts are unchanged. `pi-web-access@0.38.0` provides configurable web search and fetch tools; its `toolActivation` defaults to `auto`, choosing eager or dynamic tool activation per model. It adds structured search/fetch data for codemode and an optional, manually started `pi-web-access-mcp` stdio CLI; installing the aggregate does not start that server. Degoog, Keenable, and the new Ceramic provider are explicit-only, excluded from automatic and `all` selection. OpenAI search now defaults to `gpt-6-luna`, results and clone cleanup are scoped per extension instance, and the promoted `@modelcontextprotocol/sdk@^1.32.1` moves the bundle off GHSA-6qxp-vccf-f47h. Perplexity search now uses the Search API's ranked pages and snippets rather than a Sonar-generated answer; requests requiring prose still use Sonar. `pi-antigravity@0.10.0` reads Pi 0.86+ transcript system messages, so Antigravity requests carry Pi's system prompt and tools; it also registers `google_search` and `generate_image` tools that use the signed-in Antigravity account. `pi-provider-qoder@0.5.0` registers the `qoder` and `qoder-cn` model providers. Sign in with `/login qoder` (browser or a personal access token from [qoder.com/account/integrations](https://qoder.com/account/integrations)) or `/login qoder-cn` (token from [qoder.com.cn/account/integrations](https://qoder.com.cn/account/integrations)). `QODER_PERSONAL_ACCESS_TOKEN` and `QODERCN_PERSONAL_ACCESS_TOKEN` log those providers in at startup. `/qoder-usage footer on` replaces the status-bar footer for that session, so leave it off while the pi-cc footer is in use. Preferred Thinking 1.0.2 preserves an explicit subagent `--thinking` choice. Deprecated `@tifan/pi-titlebar-spinner` is no longer bundled; Rename remains the single owner of Herdr tab naming.
 
 `pi-stash` is no longer bundled: `/btw` already preserves the main editor draft while handling side questions outside the main conversation. Prior `@herbertgao/pi-stash` releases remain available but are no longer maintained here.
 
@@ -85,12 +85,6 @@ For the intended compact status text, merge the optional pi-lens widget setting
 
 Pi 0.85.1 or newer should use native `fullscreen` TUI mode.
 
-### Remote Pi trust boundary
-
-Configure `REMOTE_PI_RELAY` to a private relay, preferably reachable only through Tailscale or another private network, **before** first running `/remote-pi`. TLS/Tailscale protects traffic in transit but the relay process can read routed content; `remote-pi@0.7.0` is not end-to-end encrypted.
-
-Known accepted `0.7.0` limitations: pairing URI/token data is persisted in Pi session data and may enter model context during its short validity window; local broker/supervisor IPC trusts processes running as the same OS user; cancelling first-time setup can retain its cwd lock until Pi exits. Do not use the public relay or run untrusted local processes if those boundaries are unacceptable.
-
 See the [repository README](https://github.com/HerbertGao/pi-extensions#readme) for the complete package list and provenance.
 
 ## License

package/THIRD_PARTY_NOTICES.md

@@ -62,7 +62,7 @@ SOFTWARE.
 
 ## `@narumitw/pi-caffeinate`
 
-The aggregate bundles [`@narumitw/pi-caffeinate`](https://github.com/narumiruna/pi-extensions/tree/main/packages/pi-caffeinate) version 0.49.10 under its original MIT license:
+The aggregate bundles [`@narumitw/pi-caffeinate`](https://github.com/narumiruna/pi-extensions/tree/main/packages/pi-caffeinate) version 0.49.11 under its original MIT license:
 
 MIT License
 
@@ -238,3 +238,7 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.
+
+## `pi-provider-qoder`
+
+The aggregate bundles [`pi-provider-qoder`](https://github.com/simonsmh/pi-provider-qoder) version 0.5.0 under its original package name. npm metadata and the repository README declare the MIT license. The published tarball does not include a LICENSE file. The published package corresponds to git commit [`2e29cbbda03862e20f216c5ecbb6c6042a6cabd7`](https://github.com/simonsmh/pi-provider-qoder/commit/2e29cbbda03862e20f216c5ecbb6c6042a6cabd7).

package/node_modules/@herbertgao/pi-subagents/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.19.0
+
+### Minor Changes
+
+- [#273](https://github.com/HerbertGao/pi-extensions/pull/273) [`e6ee379`](https://github.com/HerbertGao/pi-extensions/commit/e6ee379393c9f5dde67955d4c28da650835d857f) Thanks [@HerbertGao](https://github.com/HerbertGao)! - Rebase `@herbertgao/pi-subagents` onto upstream v0.20.0 (`13106ab`) and adopt upstream's own mention-clone rewrite: the clone takes its history through `SessionManager.inMemory` and receives the live system prompt through a `DefaultResourceLoader` override instead of the previous context-projection path. The local behavior that hands the spawn the main session's context augmented with the clone's `tools` and `executeTool` is retained, so mentioned agents keep Pi 1.x tool-call capabilities while staying attributed to the main session.
+
+  Two local patches remain because their upstream pull requests are still open: preserving a worktree when cleanup fails (`tintinweb/pi-subagents#268`, with the refused `--no-gpg-sign` preservation commit) and retaining unconsumed terminal results past the automatic cleanup timer (`tintinweb/pi-subagents#348`). Upstream now declares `typebox` as a host-provided peer and drops `@sinclair/typebox` from runtime dependencies. No installed configuration, credentials, or sessions are migrated.
+
 ## 0.18.5
 
 ### Patch Changes

package/node_modules/@herbertgao/pi-subagents/README.md

@@ -47,7 +47,7 @@ Or load directly for development:
 pi -e ./src/index.ts
 ```
 
-Requires pi **0.84.0 or newer**: the [`SubagentWorkflow`](#subagentworkflow) tool builds on `constrainedSampling` (pi 0.82.0) and pi-tui's `stripTerminalSequences` (0.84.0). The `peerDependencies` range declares it, so npm flags an older pi at install time.
+Requires pi **1.1.0 or newer**: pi 0.86 and 0.87 moved the system prompt and conversation history into the session transcript, and the `@handle` conversation clone and the agent transcript files are built on that model. The `peerDependencies` range declares it, so npm flags an older pi at install time.
 
 ### Other hosts
 

package/node_modules/@herbertgao/pi-subagents/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@herbertgao/pi-subagents",
-  "version": "0.18.5",
+  "version": "0.19.0",
   "description": "Claude Code-style autonomous subagents and workflow orchestration for Pi, with HerbertGao-maintained UI extensions.",
   "keywords": [
     "agent",
@@ -55,7 +55,6 @@
     "@earendil-works/pi-ai": "*",
     "@earendil-works/pi-coding-agent": "*",
     "@earendil-works/pi-tui": "*",
-    "@sinclair/typebox": "*",
     "typebox": "*"
   },
   "engines": {
@@ -70,9 +69,9 @@
   },
   "x-upstream": {
     "package": "@tintinweb/pi-subagents",
-    "version": "0.19.0",
-    "reviewedVersion": "0.19.0",
+    "version": "0.20.0",
+    "reviewedVersion": "0.20.0",
     "repository": "https://github.com/tintinweb/pi-subagents",
-    "commit": "95d10867f391636e6563e3885e972618083f306b"
+    "commit": "13106ab6f608b3acc54185da5299ee7fbaabb6b9"
   }
 }

package/node_modules/@herbertgao/pi-subagents/src/index.ts

@@ -35,7 +35,7 @@ import {
   Spacer,
   Text,
 } from "@earendil-works/pi-tui"
-import { Type } from "@sinclair/typebox"
+import { Type } from "typebox"
 import { abortable } from "./abortable.js"
 import { hasAgentBadge, renderAgentName } from "./agent-color.js"
 import {

package/node_modules/@herbertgao/pi-subagents/src/invocation-config.ts

@@ -1,4 +1,4 @@
-import { Type } from "@sinclair/typebox"
+import { Type } from "typebox"
 import type {
   AgentConfig,
   IsolationMode,

package/node_modules/@herbertgao/pi-subagents/src/mention-clone.ts

@@ -12,31 +12,23 @@
  * So the turn happens somewhere else. The conversation is cloned into a
  * throwaway in-memory session — same messages, same system prompt, same model —
  * and that copy takes the turn off-screen. A literal clone: the session's own
- * entries, projected by pi's own `sessionEntryToContextMessages`, not
- * `inherit_context`'s text rendering of them.
+ * entries, not `inherit_context`'s text rendering of them.
+ *
+ * Pi builds every request from the session manager, so that is where the
+ * clone's history goes: the parent's root-to-leaf entries, handed to
+ * `SessionManager.inMemory`. The clone projects them itself, compaction and
+ * branch summaries included, so a long conversation clones as what the main
+ * model is actually working from. A conversation with nothing in it yet clones
+ * to nothing in it yet, which is the correct answer rather than a failure.
  *
  * Cloned from memory rather than from the session file, which cannot be relied
  * on: `SessionManager._persist` withholds every write until the first assistant
  * message lands, so a fork taken before then reads an empty file and throws.
- * `buildSessionContext()` has no such timing, and is compaction-aware — it walks
- * the leaf path and substitutes the summary for entries folded into it, so a
- * long conversation clones as what the main model is actually working from. A
- * conversation with nothing in it yet clones to nothing in it yet, which is the
- * correct answer rather than a failure.
- *
- * It is also the oldest of the equivalent Pi APIs — `buildContextEntries` on
- * ReadonlySessionManager and the `sessionEntryToContextMessages` export both
- * arrived in 0.80.5 — where this one has been exported unchanged from before
- * the declared peer floor, and is the same code path (`byId` is only an index
- * cache, so passing it or not cannot change the result). Keeping the floor
- * honest costs nothing here: see the `compat-floor-pi` job.
  *
- * Its `thinkingLevel` is NOT used, and is the one place the newer API would be
- * better. `getSessionContextSettings` starts at "off" and moves only on an
- * explicit `thinking_level_change` entry, so a session where nobody ran
- * `/think` reports "off" rather than the level it is really using. Omitting the
- * field instead lets `createAgentSession` resolve it from settings, which is
- * that real level.
+ * The system prompt cannot ride along in those entries. Pi rebuilds it from the
+ * session's own options on every request and patches the difference over the
+ * transcript, so the parent's prompt would be replaced by the clone's. It goes
+ * in through the resource loader's prompt override instead.
  *
  * Three details make the spawn belong to the real session rather than the
  * clone:
@@ -63,8 +55,6 @@
 
 import type { Model } from "@earendil-works/pi-ai"
 import {
-  buildSessionContext,
-  convertToLlm,
   createAgentSession,
   DefaultResourceLoader,
   type ExtensionContext,
@@ -74,7 +64,7 @@ import {
 } from "@earendil-works/pi-coding-agent"
 import { runInChildSessionContext } from "./child-context.js"
 import { agentMentionReminder } from "./mention.js"
-import type { SubagentType, ThinkingLevel } from "./types.js"
+import type { SubagentType } from "./types.js"
 
 export interface MentionCloneOptions {
   /** The MAIN session's context — what the spawn is attributed to, and the
@@ -156,54 +146,40 @@ export async function runMentionClone(
     const parentModelRuntime = (
       ctx.modelRegistry as unknown as { runtime?: unknown }
     ).runtime
-    // The conversation as the main session resolves it: compaction applied,
-    // branch summaries substituted.
-    const conversation = buildSessionContext(
-      ctx.sessionManager.getEntries(),
-      ctx.sessionManager.getLeafId(),
-    )
-    // Pi 0.82.0 added this; below it the field is absent and the clone takes
-    // the settings level instead, which is what a session that never ran
-    // `/think` is on anyway. Same shim shape as `modelRuntime` below.
-    const thinkingLevel = (ctx as { thinkingLevel?: ThinkingLevel })
-      .thinkingLevel
-    const sessionManager = SessionManager.inMemory(ctx.cwd)
-    for (const entry of conversation.messages) {
-      // The live prompt is copied below. Do not replay the parent's system
-      // messages: newer Pi also stores its tool declarations there.
-      if ((entry.role as string) === "system") continue
-      // Summary messages are projections, not appendable session entries.
-      // Preserve exactly the user message Pi would send for each summary.
-      if (
-        entry.role === "compactionSummary" ||
-        entry.role === "branchSummary"
-      ) {
-        for (const message of convertToLlm([entry]))
-          sessionManager.appendMessage(message)
-      } else {
-        sessionManager.appendMessage(entry)
-      }
-    }
-    const systemPrompt = ctx.getSystemPrompt?.()
-    const created = await runInChildSessionContext(async () => {
-      const resourceLoader = new DefaultResourceLoader({
-        cwd: ctx.cwd,
-        agentDir: getAgentDir(),
-        extensionFactories: [
-          (pi) => {
-            pi.on("before_agent_start", () =>
-              systemPrompt ? { systemPrompt } : undefined,
-            )
-          },
-        ],
-      })
-      await resourceLoader.reload()
-      return createAgentSession({
+    // Absent when the session has no level of its own; the clone then takes the
+    // settings level, which is what a session that never ran `/think` is on.
+    const thinkingLevel = ctx.thinkingLevel
+    // The live system prompt, not the one the clone would build from cwd and
+    // agentDir — extensions contribute to it per turn. Everything the loader
+    // would add on top (AGENTS.md, skills, APPEND_SYSTEM.md) is already in the
+    // rendered prompt, so it is suppressed, as agent-runner does.
+    const systemPrompt = ctx.getSystemPrompt()
+    const loader = new DefaultResourceLoader({
+      cwd: ctx.cwd,
+      agentDir: getAgentDir(),
+      noExtensions: true,
+      noSkills: true,
+      noPromptTemplates: true,
+      noThemes: true,
+      noContextFiles: true,
+      systemPromptOverride: (base: string | undefined) => systemPrompt || base,
+      appendSystemPromptOverride: () => [],
+    })
+    await runInChildSessionContext(() => loader.reload())
+    const created = await runInChildSessionContext(() =>
+      createAgentSession({
         cwd: ctx.cwd,
-        // Nothing about the copy is worth persisting, and an in-memory manager
-        // is also what keeps the real session untouched.
-        sessionManager,
-        resourceLoader,
+        // The parent's root-to-leaf path, which the clone projects itself:
+        // compaction applied, branch summaries substituted. Not `getEntries()`,
+        // whose last entry is not the leaf after `/tree` navigation. In memory,
+        // so nothing about the copy is persisted and the real session stays
+        // untouched.
+        sessionManager: SessionManager.inMemory(
+          ctx.cwd,
+          undefined,
+          ctx.sessionManager.getBranch(),
+        ),
+        resourceLoader: loader,
         model: ctx.model as Model<never> | undefined,
         ...(thinkingLevel && { thinkingLevel }),
         modelRegistry: ctx.modelRegistry,
@@ -220,8 +196,8 @@ export async function runMentionClone(
         // agent-runner's `tools: sessionTools` beside its nested `customTools`.
         tools: [cloneAgentTool.name],
         customTools: [cloneAgentTool],
-      } as Parameters<typeof createAgentSession>[0])
-    })
+      } as Parameters<typeof createAgentSession>[0]),
+    )
     session = created.session
 
     // User text first, reminder after — the order Claude Code's attachment

package/node_modules/@herbertgao/pi-subagents/src/nested-tools.ts

@@ -6,7 +6,7 @@ import {
   type ExtensionContext,
   type ToolDefinition,
 } from "@earendil-works/pi-coding-agent"
-import { Type } from "@sinclair/typebox"
+import { Type } from "typebox"
 import { abortable } from "./abortable.js"
 import {
   buildAgentRegistry,

package/node_modules/@herbertgao/pi-subagents/src/output-file.ts

@@ -122,17 +122,27 @@ export function streamToOutputFile(
   cwd: string,
   startIndex?: number,
 ): () => void {
-  // Index of the first message this stream is responsible for. A spawn writes
-  // messages[0] as the initial prompt entry, so it starts at 1. A resume hands
+  // Index of the first message this stream is responsible for. A resume hands
   // in the session's length as of just before the run: the session already
   // holds every prior turn, and re-emitting those would duplicate history that
-  // is already in the file.
-  let writtenCount = startIndex ?? 1
+  // is already in the file. A spawn has already written its prompt as the
+  // initial entry, so it starts after the first user message — found on the
+  // first flush, because pi puts a system message ahead of it and adds both
+  // only once the prompt runs.
+  let writtenCount = startIndex
 
   const flush = () => {
     const messages = session.messages
+    if (writtenCount === undefined) {
+      const prompt = messages.findIndex((m) => m.role === "user")
+      if (prompt === -1) return
+      writtenCount = prompt + 1
+    }
     while (writtenCount < messages.length) {
-      const msg = messages[writtenCount]
+      const msg = messages[writtenCount++]
+      // Pi's prompt and tool-loadout records; a Claude Code transcript has no
+      // such entry.
+      if (msg.role === "system") continue
       const entry = {
         isSidechain: true,
         agentId,
@@ -151,7 +161,6 @@ export function streamToOutputFile(
       } catch {
         /* ignore write errors */
       }
-      writtenCount++
     }
   }
 

package/node_modules/@herbertgao/pi-subagents/src/workflow/collisions.ts

@@ -46,11 +46,14 @@ import { SUBAGENT_TOOL_NAMES } from "../agent-runner.js"
  *
  * Our own name, because pi resolves a duplicate registration silently, and
  * Claude Code's bare `Workflow`, because a port of that tool is what a second
- * workflow extension most likely calls itself.
+ * workflow extension most likely calls itself. Lowercase `workflow` is the same
+ * tool by pi convention: it is what `@quintinshaw/pi-dynamic-workflows`
+ * registers, and the match here is exact, so the case has to be listed by hand.
  */
 export const FOREIGN_WORKFLOW_TOOL_NAMES: ReadonlySet<string> = new Set([
   SUBAGENT_TOOL_NAMES.WORKFLOW,
   "Workflow",
+  "workflow",
 ])
 
 /** The fields of a registered tool this decision reads. */

package/node_modules/@herbertgao/pi-subagents/src/workflow/json-schema.ts

@@ -7,14 +7,15 @@
  *
  * ## Which typebox
  *
- * **`typebox`, not `@sinclair/typebox`.** They are different packages and both
- * are installed here. `@sinclair/typebox` (0.34) dispatches on a `Kind` symbol
- * that a schema arriving over the wire does not carry, so `Value.Check` throws
- * `Unknown type` on a plain JSON Schema — and `Type.Unsafe` does not help, it
- * stamps a `Kind` that is not registered. `typebox` v1 is a standards JSON
- * Schema validator and takes the schema as-is. It is also the package pi itself
- * types `ToolDefinition.parameters` against, so the same schema object serves
- * both roles with no conversion.
+ * **`typebox`, not `@sinclair/typebox`.** They are different packages.
+ * `@sinclair/typebox` (0.34) dispatches on a `Kind` symbol that a schema
+ * arriving over the wire does not carry, so `Value.Check` throws `Unknown type`
+ * on a plain JSON Schema — and `Type.Unsafe` does not help, it stamps a `Kind`
+ * that is not registered. `typebox` v1 is a standards JSON Schema validator and
+ * takes the schema as-is. It is also the package pi itself types
+ * `ToolDefinition.parameters` against and supplies to extensions at runtime
+ * (a peer dependency here), so the same schema object serves both roles with no
+ * conversion.
  *
  * ## Why we validate at all
  *

package/node_modules/@narumitw/pi-caffeinate/dist/index.ts

@@ -12,7 +12,12 @@ var INHIBIT_APPLICATION_NAME = "pi-caffeinate";
 var SCREENSAVER_OBJECT_PATHS = ["/org/freedesktop/ScreenSaver", "/ScreenSaver"];
 var DBUS_CALL_TIMEOUT_MS = 2e3;
 async function defaultDbusScreenSaverFactory() {
-  const { sessionBus } = await import("dbus-native");
+  const dbus = await import("dbus-native");
+  const namespaceSessionBus = "sessionBus" in dbus ? dbus.sessionBus : void 0;
+  const sessionBus = typeof namespaceSessionBus === "function" ? namespaceSessionBus : dbus.default?.sessionBus;
+  if (typeof sessionBus !== "function") {
+    throw new Error("dbus-native did not export sessionBus");
+  }
   return new NativeScreenSaverClient(sessionBus());
 }
 var NativeScreenSaverClient = class {