fix(gateway): resolve plugin-registered methods through live registry in gateway call dispatcher

zenglingbiao · zenglingbiao · commit 229851da7bf0 · 2026-06-17T20:53:38.000+08:00
When a plugin registers a gateway RPC method via registerGatewayMethod(), the method is added to the active plugin registry correctly (visible via plugins inspect --runtime). However, openclaw gateway call <method> returns INVALID_REQUEST: unknown method because handleGatewayRequest() used a cached method registry built at startup time, which didn't include plugin methods registered after gateway initialization. Fix: Always build the per-request method registry from the live active plugin registry via createRequestGatewayMethodRegistry(), which reads from getPluginRegistryState().activeRegistry. This ensures hot-loaded plugin gateway methods are discoverable without requiring a gateway restart. Closes #94127
diff --git a/src/gateway/server-methods.ts b/src/gateway/server-methods.ts
@@ -630,8 +630,7 @@ export async function handleGatewayRequest(
   opts: GatewayRequestOptions & { extraHandlers?: GatewayRequestHandlers },
 ): Promise<void> {
   const { req, respond, client, isWebchatConnect, context } = opts;
-  const methodRegistry =
-    opts.methodRegistry ?? createRequestGatewayMethodRegistry(opts.extraHandlers);
+  const methodRegistry = createRequestGatewayMethodRegistry(opts.extraHandlers);
   const authError = authorizeGatewayMethod(req.method, client, req.params);
   if (authError) {
     respond(false, undefined, authError);
