@omercnet/paseo-omp 2.0.1-next.256.1 → 2.0.1-next.258.1

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
@@ -100,7 +100,7 @@ Provider functionality outside the capability flags is tracked separately:
100
100
  | Models, modes, and thinking catalog | **100%** | Native catalog is mapped to opaque public model IDs with committed defaults and permission-gated modes. |
101
101
  | Connection `send` / `onEvent` / `close` lifecycle | **100%** | Request correlation, multi-session ownership, process recovery, teardown, and provider reload/removal are covered. |
102
102
  | Session launch: cwd, env, system prompt, title, and persistence | **100%** | Complete launch configuration is bounded, validated, forwarded, and re-read on recovery; selected host and profile daemon environment values are resolved only when catalog and session children spawn. |
103
- | MCP server forwarding and host tools | **100%** | Configured MCP tools are discovered, namespaced, labeled, executed, canceled, and bounded. Caller-scoped Paseo orchestration tools retain their native names, such as `create_agent` and `list_profiles`, so OMP skills can invoke them directly. The MCP composer control delegates native server management to OMP instead of duplicating its profile and workspace precedence. Exact `toolPolicy` remains the separate 0% capability above. |
103
+ | MCP server forwarding and host tools | **100%** | Configured MCP tools are discovered, namespaced, labeled, executed, canceled, and bounded. Forwarded tools are namespaced `mcpx__<server>_<tool>`: OMP treats `mcp__` as its own MCP manager's namespace and deletes that whole namespace from the session registry on every `refreshMCPTools`, so a forwarded tool registered under it is accepted and then dropped. Registration races OMP's deferred MCP discovery on every supported release; from 18.9.0 the ordering is deterministic and the tools were always lost. An OMP approval policy or inline-docs glob keyed on the old `mcp__<server>_<tool>` spelling must be re-keyed to `mcpx__<server>_<tool>`; OMP matches approval entries by exact tool name. Caller-scoped Paseo orchestration tools retain their native names, such as `create_agent` and `list_profiles`, so OMP skills can invoke them directly. The MCP composer control delegates native server management to OMP instead of duplicating its profile and workspace precedence. Exact `toolPolicy` remains the separate 0% capability above. |
104
104
  | Denied native tools | **100%** | `disallowedTools` becomes an explicit OMP allow-list; unknown names fail closed. |
105
105
  | Commands and committed session state events | **100%** | Publishes `session.commands`, `session.opened`, `session.config`, `session.ready`, and request completion in protocol order. |
106
106
  | Built-in timeline snapshots | **100%** | Assistant, reasoning, tools, todos, notifications, errors, compaction, and friendly MCP labels use stable IDs and complete snapshots. OMP emits client-safe PNG/JPEG when possible; validated legacy WebP images render on capable clients with an explicit per-image fallback elsewhere. |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@omercnet/paseo-omp",
3
- "version": "2.0.1-next.256.1",
3
+ "version": "2.0.1-next.258.1",
4
4
  "type": "module",
5
5
  "description": "Paseo integration for OMP, including its direct provider and workspace tooling.",
6
6
  "license": "MIT",
@@ -63,8 +63,8 @@
63
63
  "@getpaseo/client": "0.11.1",
64
64
  "@getpaseo/plugin": "0.11.1",
65
65
  "@getpaseo/server": "0.11.1",
66
- "@oh-my-pi/pi-agent-core": "18.8.4",
67
- "@oh-my-pi/pi-coding-agent": "18.8.4",
66
+ "@oh-my-pi/pi-agent-core": "18.10.1",
67
+ "@oh-my-pi/pi-coding-agent": "18.10.1",
68
68
  "@tanstack/react-query": "^5.102.3",
69
69
  "@types/node": "^24.10.1",
70
70
  "@types/react": "^19.2.18",
@@ -1,2 +1,2 @@
1
1
  /** Release Please keeps this bundle-safe constant aligned with package.json. */
2
- export const PASEO_OMP_PACKAGE_VERSION = "2.0.1-next.256.1"; // x-release-please-version
2
+ export const PASEO_OMP_PACKAGE_VERSION = "2.0.1-next.258.1"; // x-release-please-version
@@ -259,11 +259,26 @@ function serverNamespaces(servers: readonly ClassifiedServer[]): ReadonlyMap<str
259
259
  );
260
260
  }
261
261
 
262
+ /**
263
+ * Namespace prefix for tools this plugin registers through `set_host_tools`.
264
+ *
265
+ * It deliberately avoids OMP's `mcp__` prefix. OMP treats that prefix as its own
266
+ * MCP manager's namespace (`isMCPToolName`), and every `refreshMCPTools` deletes
267
+ * the whole namespace from the session tool registry before rebuilding it from
268
+ * manager- and extension-owned tools only. Host tools registered over RPC are in
269
+ * neither set, so an `mcp__` name is accepted and then dropped once OMP's own
270
+ * deferred MCP discovery completes, leaving the tool callable from nowhere.
271
+ */
272
+ export const HOST_TOOL_NAME_PREFIX = "mcpx__";
273
+
274
+ /** Prefix used before {@link HOST_TOOL_NAME_PREFIX}; still rendered in persisted timelines. */
275
+ export const LEGACY_HOST_TOOL_NAME_PREFIX = "mcp__";
276
+
262
277
  function exposedToolName(server: ClassifiedServer, namespace: string, toolName: string): string {
263
278
  const tool = safeName(toolName, "tool");
264
279
  if (server.canonical) return tool;
265
280
  const unprefixed = tool.startsWith(`${namespace}_`) ? tool.slice(namespace.length + 1) : tool;
266
- const base = `mcp__${namespace}_${unprefixed}`;
281
+ const base = `${HOST_TOOL_NAME_PREFIX}${namespace}_${unprefixed}`;
267
282
  if (utf8Bytes(base) <= MAX_HOST_TOOL_NAME_BYTES) return base;
268
283
  const suffix = digest(`${server.name}\0${toolName}`);
269
284
  return `${base.slice(0, MAX_HOST_TOOL_NAME_BYTES - suffix.length - 1)}_${suffix}`;
@@ -5,6 +5,7 @@ import type {
5
5
  ProviderToolCallDetail,
6
6
  } from "@getpaseo/plugin/server/provider";
7
7
  import { OMP_MCP_AUTH_TIMELINE_KIND } from "../../shared/mcp";
8
+ import { HOST_TOOL_NAME_PREFIX, LEGACY_HOST_TOOL_NAME_PREFIX } from "./host-tools";
8
9
  import { isOmpImageMimeType, isValidImagePayload, type OmpImageMimeType } from "./image";
9
10
  import {
10
11
  OMP_MAX_CONTENT_PARTS,
@@ -189,8 +190,15 @@ function xdeviceToolName(nativeName: string, input: JsonValue): string | undefin
189
190
  const match = path?.match(/^xd:\/\/([A-Za-z0-9_][A-Za-z0-9_.-]{0,255})(?:[/?#]|$)/u);
190
191
  return match?.[1];
191
192
  }
193
+ function hostToolPrefixOf(name: string): string | undefined {
194
+ if (name.startsWith(HOST_TOOL_NAME_PREFIX)) return HOST_TOOL_NAME_PREFIX;
195
+ // Timelines persisted before the rename still carry the legacy prefix.
196
+ if (name.startsWith(LEGACY_HOST_TOOL_NAME_PREFIX)) return LEGACY_HOST_TOOL_NAME_PREFIX;
197
+ return undefined;
198
+ }
192
199
  function friendlyXdeviceToolName(name: string): string {
193
- const routedName = name.startsWith("mcp__") ? name.slice("mcp__".length) : name;
200
+ const prefix = hostToolPrefixOf(name);
201
+ const routedName = prefix ? name.slice(prefix.length) : name;
194
202
  const words = routedName
195
203
  .replace(/[-_.]+/gu, " ")
196
204
  .replace(/\s+/gu, " ")
@@ -541,7 +549,7 @@ export class OmpTimelineProjector {
541
549
  const routedToolName = xdeviceToolName(event.toolName, input);
542
550
  const displayName =
543
551
  this.hostToolLabels.get(routedToolName ?? event.toolName) ??
544
- (routedToolName || event.toolName.startsWith("mcp__")
552
+ (routedToolName || hostToolPrefixOf(event.toolName)
545
553
  ? friendlyXdeviceToolName(routedToolName ?? event.toolName)
546
554
  : event.toolName);
547
555
  const snapshot: ToolSnapshot = {