OPENCLAW_EXTENSION_API_DEPRECATED warning after OpenClaw 2026.4.2 upgrade

[elsatheassist-crypto]

Environment

• OpenClaw version: 2026.4.2
• Plugin version: memory-lancedb-pro v1.1.0-beta.10
• OS: macOS (arm64)

Description

After upgrading to OpenClaw 2026.4.2, the following deprecation warning is emitted on every startup:

(node:69143) [OPENCLAW_EXTENSION_API_DEPRECATED] Warning: openclaw/extension-api is deprecated. Migrate to api.runtime.agent.* or focused openclaw/plugin-sdk/<subpath> imports. See https://docs.openclaw.com/plugins/sdk-migration

This compatibility bridge is temporary. Bundled plugins should use the injected plugin runtime instead of importing host-side agent helpers directly. Migration guide: https://docs.openclaw.com/plugins/sdk-migration

Root Cause

In index.ts, the getExtensionApiImportSpecifiers() function (line 375-393) dynamically imports openclaw/dist/extensionAPI.js as a fallback resolution path:

specifiers.push("openclaw/dist/extensionAPI.js");
specifiers.push(toImportSpecifier(requireFromHere.resolve("openclaw/dist/extensionAPI.js")));
// ... plus hardcoded system paths

OpenClaw 2026.4.2 now warns when bundled plugins load via this deprecated bridge.

Impact

• Log noise only — no functional issues observed
• The warning appears on every startup/restart

Request

Migrate the runtime import from openclaw/dist/extensionAPI.js to the new openclaw/plugin-sdk subpath imports as per the migration guide. The plugin already uses openclaw/plugin-sdk for type imports — the runtime import path just needs to catch up.

Additional Context

• No existing issues or PRs found addressing this
• OpenClaw docs indicate the extensionAPI.js bridge is temporary and will be removed in a future release

[AliceLJY]

Thanks for the clear report and root-cause analysis.

This is a known side effect of the OpenClaw 2026.4.2 SDK restructuring. The plugin's runtime fallback path still resolves through the deprecated openclaw/dist/extensionAPI.js bridge — the type-level imports already use openclaw/plugin-sdk but the runtime path didn't follow.

Triage:

• Priority: Low (log noise only, no functional impact)
• Fix: Migrate the runtime import specifiers in getExtensionApiImportSpecifiers() to openclaw/plugin-sdk/<subpath> equivalents

We'll get to this as part of the 4.2 compatibility pass. If you'd like to submit a PR, the change is fairly localized — just the specifier list in index.ts lines 375-393 needs updating per the migration guide.

[AliceLJY]

Informational warning from OpenClaw 2026.4.2 SDK restructuring. Does not affect plugin functionality. No action needed on our side.