fix(plugins): keep built plugin loading on one module graph by huntharo · Pull Request #48595 · openclaw/openclaw

huntharo · 2026-03-17T00:43:41Z

Summary

Describe the problem and fix in 2–5 bullets:

Problem: built plugin loading could still create multiple OpenClaw runtime graphs in memory. JITI was re-transpiling built dist/*.js modules, dist/plugins/runtime/index.js was not emitted in the main dist graph, and dist-runtime hard-linked JS under a second path. That split singleton state such as plugin command registration and runtime globals across separate module identities.
Why it matters: plugin commands registered during startup could land in one graph while Telegram command discovery/execution read from another. In practice this broke bundled plugin commands such as /voice, /phone, and /pair, which should now show up again in Telegram. The same duplicate-graph setup also drove the slow startup path that previously spent about 70 seconds at 100% CPU on one core.
What changed: plugin JITI boundaries now prefer native loading for built JS, the main dist build now emits plugins/runtime/index.js in the unified graph with plugin-sdk/*, bundled plugins, and bundled hooks, and dist-runtime now stages JS as thin wrapper modules that forward to canonical dist/... entrypoints instead of hard-linking a second executable graph. Bundled plugin metadata needed for discovery is still copied into dist-runtime.
What did NOT change (scope boundary): this does not change plugin manifests, plugin command semantics, or bundled plugin feature behavior beyond restoring the correct shared runtime/module identity and removing the duplicate-graph startup work.

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Closes #
Related #

User-visible / Behavior Changes

Bundled plugin commands from Telegram-facing plugins now register against the canonical shared runtime graph, so /voice, /phone, and /pair show up again in Telegram.
Built startup paths no longer construct the previous duplicate module/runtime graph shape, which resolves the prior startup behavior that could sit at about 70 seconds with one CPU core pegged.
dist-runtime still exposes bundled plugins, but its JS entries now forward into canonical dist/... modules instead of materializing a second executable JS tree.

Security Impact (required)

New permissions/capabilities? (Yes/No) No
Secrets/tokens handling changed? (Yes/No) No
New/changed network calls? (Yes/No) No
Command/tool execution surface changed? (Yes/No) No
Data access scope changed? (Yes/No) No
If any Yes, explain risk + mitigation:

Repro + Verification

Environment

OS: macOS
Runtime/container: Node 22+, local repo build
Model/provider: N/A
Integration/channel (if any): bundled plugins, Telegram command registration, gateway startup
Relevant config (redacted): default local build output using dist/ and dist-runtime/

Steps

Build OpenClaw and start the built gateway/plugin loading path.
Load bundled plugins that register commands and inspect the runtime/build layout used by plugin discovery and execution.
Verify that plugin commands register into the same runtime graph used by Telegram command listing/dispatch and that startup no longer materializes the duplicate dist-runtime JS graph.

Expected

Built plugin loading uses one canonical runtime/module graph.
Bundled plugin commands such as /voice, /phone, and /pair appear in Telegram.
Startup avoids the prior duplicate-graph work and no longer hits the previous ~70 second single-core CPU burn.

Actual

JITI could re-transpile built dist/*.js into a second graph.
plugins/runtime/index was missing from the main dist graph, so built loading could fall back to source/runtime duplication paths.
dist-runtime hard-linked executable JS under a second path, so Node still treated those modules as distinct identities even when the bytes were shared.

Evidence

Attach at least one:

Failing test/log before + passing after
Trace/log snippets
Screenshot/recording
Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

Verified scenarios: ran pnpm build; ran pnpm test -- src/plugin-sdk/root-alias.test.ts src/plugins/loader.test.ts; ran pnpm test -- src/plugins/loader.test.ts src/plugins/stage-bundled-plugin-runtime.test.ts src/infra/tsdown-config.test.ts; verified dist/plugins/runtime/index.js now exists; verified dist-runtime/extensions/openai/index.js is a wrapper that re-exports from dist/extensions/openai/index.js; verified dist-runtime regular files are no longer hard-linked executable duplicates.
Edge cases checked: loader still prefers dist runtime when running from dist; transpiler-cache resolution still falls back correctly; bundled plugin discovery still works from dist-runtime because package.json and openclaw.plugin.json are copied while other non-JS assets stay linked.
What you did not verify: I did not run a full end-to-end Telegram bot session in this draft workspace, and I did not capture a fresh startup timing trace in this PR body beyond the structural/runtime fixes above.

Review Conversations

I replied to or resolved every bot review conversation I addressed in this PR.
I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

Backward compatible? (Yes/No) Yes
Config/env changes? (Yes/No) No
Migration needed? (Yes/No) No
If yes, exact upgrade steps:

Failure Recovery (if this breaks)

How to disable/revert this change quickly: revert this PR or restore the previous build/runtime staging behavior by rolling back the JITI loader config, unified dist entry changes, and runtime overlay wrapper generation.
Files/config to restore: src/plugins/loader.ts, src/plugin-sdk/root-alias.cjs, tsdown.config.ts, scripts/stage-bundled-plugin-runtime.mjs
Known bad symptoms reviewers should watch for: plugin commands missing again in Telegram, bundled plugins resolving different runtime singletons, dist-runtime reappearing as a second executable JS graph, startup CPU time regressing toward the previous 70 second single-core burn.

Risks and Mitigations

List only real risks for this PR. Add/remove entries as needed. If none, write None.

Risk: changing the build graph could perturb chunk layout or lazy runtime entry resolution for bundled plugins.
Mitigation: added focused tests for tsdown graph shape, dist runtime resolution, runtime overlay generation, and bundled plugin discovery from dist-runtime; also verified pnpm build succeeds with the new graph.
Risk: dist-runtime wrapper modules could break plugin discovery if package metadata is no longer available under the runtime overlay.
Mitigation: package.json and openclaw.plugin.json are copied into dist-runtime, and the discovery test verifies setupEntry and startup metadata still resolve correctly.

greptile-apps · 2026-03-17T00:48:45Z

Greptile Summary

This PR fixes a dual-module-graph problem in OpenClaw's built plugin loading path. Three root causes were addressed together: JITI was re-transpiling pre-built dist/*.js files into a second module graph (tryNative: true added to both loader boundaries), dist/plugins/runtime/index.js was absent from the main dist graph (promoted into the unified tsdown entry), and dist-runtime materialised a full hard-linked copy of dist/ (replaced with thin ESM wrapper modules that forward to canonical dist/ paths). Together these changes ensure plugin singleton state — command registries, runtime globals — is always held in one canonical dist/ module identity regardless of which path code is loaded through.

Key changes:

scripts/stage-bundled-plugin-runtime.mjs: replaces mirrorTreeWithHardlinks with stagePluginRuntimeOverlay; .js files become ESM wrapper modules (export * from …canonical…), plugin metadata files are copied, other assets are symlinked.
tsdown.config.ts: three separate build configs (core, plugin-sdk, bundled plugins/hooks) merged into one unified entry map so all runtime singletons are emitted once into dist/.
src/plugins/loader.ts / src/plugin-sdk/root-alias.cjs: tryNative: true added to JITI options to prefer Node's native ESM loader for pre-built JS.
Tests: four new or substantially updated test files cover tsdown graph shape, JITI option propagation, wrapper forwarding behaviour (including a live dynamic import), metadata copy/symlink policy, and end-to-end plugin discovery from dist-runtime.

One minor observation: writeRuntimeModuleWrapper always emits export default module.default, which exports undefined as default for modules that have no default export. This is a widely-accepted re-export wrapper pattern and is unlikely to cause real issues here, but it could confuse interop code that distinguishes "no default" from "default is undefined" (see inline comment).

Confidence Score: 4/5

Safe to merge; structural changes are well-tested and the design correctly eliminates the duplicate module graph without altering plugin semantics.
The core fix (unified tsdown graph + tryNative + wrapper modules) is architecturally sound and each piece has focused unit tests including a live ESM dynamic-import round-trip for the wrapper. The one minor open question is the unconditional export default module.default for modules with no default export, which is benign in the current codebase but slightly surprising. End-to-end Telegram bot verification was not performed in this PR (noted by the author), leaving a small gap in confidence for the Telegram command registration path specifically.
scripts/stage-bundled-plugin-runtime.mjs — specifically writeRuntimeModuleWrapper and how the unconditional default re-export interacts with any bundled plugin that checks for the presence of a default export on a namespace import.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: scripts/stage-bundled-plugin-runtime.mjs
Line: 40-43

Comment:
**Wrapper unconditionally exports `default` for all JS modules**

`export * from specifier` does not re-export `default` in ESM, so the explicit `export default module.default` is necessary for modules that do have a default export. However, for modules with no default export `module.default` is `undefined`, meaning the wrapper will export `undefined` as `default`. This makes `'default' in moduleNamespace` evaluate to `true` even when the canonical `dist/` module has no default, which can confuse interop code that distinguishes "no default" from "default is undefined".

A guard makes the intent explicit and avoids the phantom default:

```suggestion
      `export * from ${JSON.stringify(normalizedSpecifier)};`,
      `import * as module from ${JSON.stringify(normalizedSpecifier)};`,
      `if (module.default !== undefined) { Object.defineProperty(exports, "default", { get: () => module.default }); }`,
```

Or, more idiomatically using a re-export conditional:

```js
// only emit the default line when you know the source has one,
// or accept the current behavior and document it explicitly:
export * from "../../../dist/extensions/diffs/index.js";
import * as module from "../../../dist/extensions/diffs/index.js";
export default module.default; // undefined for modules with no default — intentional
```

Not a blocker if the project never checks `'default' in namespace`, but worth an explicit comment if the unconditional `undefined` default is intentional.

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: aa802a6}

greptile-apps · 2026-03-17T00:48:49Z

scripts/stage-bundled-plugin-runtime.mjs

+      `export * from ${JSON.stringify(normalizedSpecifier)};`,
+      `import * as module from ${JSON.stringify(normalizedSpecifier)};`,
+      "export default module.default;",
+      "",


Wrapper unconditionally exports default for all JS modules

export * from specifier does not re-export default in ESM, so the explicit export default module.default is necessary for modules that do have a default export. However, for modules with no default export module.default is undefined, meaning the wrapper will export undefined as default. This makes 'default' in moduleNamespace evaluate to true even when the canonical dist/ module has no default, which can confuse interop code that distinguishes "no default" from "default is undefined".

A guard makes the intent explicit and avoids the phantom default:

Suggested change

`export * from ${JSON.stringify(normalizedSpecifier)};`,

`import * as module from ${JSON.stringify(normalizedSpecifier)};`,

"export default module.default;",

"",

`export * from ${JSON.stringify(normalizedSpecifier)};`,

`import * as module from ${JSON.stringify(normalizedSpecifier)};`,

`if (module.default !== undefined) { Object.defineProperty(exports, "default", { get: () => module.default }); }`,

Or, more idiomatically using a re-export conditional:

// only emit the default line when you know the source has one, // or accept the current behavior and document it explicitly: export * from "../../../dist/extensions/diffs/index.js"; import * as module from "../../../dist/extensions/diffs/index.js"; export default module.default; // undefined for modules with no default — intentional

Not a blocker if the project never checks 'default' in namespace, but worth an explicit comment if the unconditional undefined default is intentional.

Prompt To Fix With AI

This is a comment left during a code review. Path: scripts/stage-bundled-plugin-runtime.mjs Line: 40-43 Comment: **Wrapper unconditionally exports `default` for all JS modules** `export * from specifier` does not re-export `default` in ESM, so the explicit `export default module.default` is necessary for modules that do have a default export. However, for modules with no default export `module.default` is `undefined`, meaning the wrapper will export `undefined` as `default`. This makes `'default' in moduleNamespace` evaluate to `true` even when the canonical `dist/` module has no default, which can confuse interop code that distinguishes "no default" from "default is undefined". A guard makes the intent explicit and avoids the phantom default: ```suggestion `export * from ${JSON.stringify(normalizedSpecifier)};`, `import * as module from ${JSON.stringify(normalizedSpecifier)};`, `if (module.default !== undefined) { Object.defineProperty(exports, "default", { get: () => module.default }); }`, ``` Or, more idiomatically using a re-export conditional: ```js // only emit the default line when you know the source has one, // or accept the current behavior and document it explicitly: export * from "../../../dist/extensions/diffs/index.js"; import * as module from "../../../dist/extensions/diffs/index.js"; export default module.default; // undefined for modules with no default — intentional ``` Not a blocker if the project never checks `'default' in namespace`, but worth an explicit comment if the unconditional `undefined` default is intentional. How can I resolve this? If you propose a fix, please make it concise.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: aa802a6390

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-03-17T00:50:11Z

scripts/stage-bundled-plugin-runtime.mjs

+      continue;
+    }
+
+    symlinkPath(sourcePath, targetPath);


Add non-symlink fallback for runtime overlay files

stagePluginRuntimeOverlay now routes every non-.js/non-metadata file through fs.symlinkSync with no fallback, so on Windows hosts that do not have symlink privilege (common for non-admin accounts without Developer Mode) scripts/runtime-postbuild.mjs will throw EPERM and pnpm build cannot complete. The previous implementation handled filesystem/link limitations by falling back to copy semantics, and this regression was introduced when hardlink/copy mirroring was replaced with unconditional file symlinks.

Useful? React with 👍 / 👎.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 18baf0a865

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-03-17T01:09:30Z

scripts/stage-bundled-plugin-runtime.mjs

+      `export * from ${JSON.stringify(normalizedSpecifier)};`,
+      `import * as module from ${JSON.stringify(normalizedSpecifier)};`,
+      "export default module.default;",


Keep bundled plugin module resolution rooted in dist-runtime

Generating wrappers that forward dist-runtime/extensions/*/*.js to dist/extensions/*/*.js changes Node’s resolution base to the dist tree, so bare imports no longer see the dist-runtime/extensions/<plugin>/node_modules symlink created later in linkPluginNodeModules. In plugins whose dependencies are installed only in plugin-local node_modules (the intended extension install shape), loading the wrapper now fails with ERR_MODULE_NOT_FOUND; the previous hardlink-based runtime path resolved those dependencies correctly because execution stayed under dist-runtime.

Useful? React with 👍 / 👎.

…#48595)

@MoerAI

* refactor: make setup the primary wizard surface * test: move setup surface coverage * docs: prefer setup wizard command * fix: follow up shared interactive regressions (openclaw#47715) * fix(plugins): resolve lazy runtime from package root * fix(daemon): accept 'Last Result' schtasks key variant on Windows (openclaw#47726) Some Windows locales/versions emit 'Last Result' instead of 'Last Run Result' in schtasks output, causing gateway status to falsely report 'Runtime: unknown'. Fall back to the shorter key when the canonical key is absent. * fix: accept schtasks Last Result key on Windows (openclaw#47844) (thanks @MoerAI) * refactor(plugins): move auth profile hooks into providers * fix: resume orphaned subagent sessions after SIGUSR1 reload Closes openclaw#47711 After a SIGUSR1 gateway reload aborts in-flight subagent LLM calls, the gateway now scans for orphaned sessions and sends a synthetic resume message to restart their work. Also makes the deferral timeout configurable via gateway.reload.deferralTimeoutMs (default: 5 minutes, up from 90s). * fix: address Greptile review feedback - Remove unrelated pnpm-lock.yaml changes - Move abortedLastRun flag clearing to AFTER successful resume (prevents permanent session loss on transient gateway failures) - Use dynamic import for orphan recovery module to avoid startup memory overhead - Add test assertion that flag is preserved on resume failure * fix: add retry with exponential backoff for orphan recovery Addresses Codex review feedback — if recovery fails (e.g. gateway still booting), retries up to 3 times with exponential backoff (5s → 10s → 20s) before giving up. * fix: address all review comments on PR openclaw#47719 + implement resume context and config idempotency guard * fix: address 6 review comments on PR openclaw#47719 1. [P1] Treat remap failures as resume failures — if replaceSubagentRunAfterSteer returns false, do NOT clear abortedLastRun, increment failed count. 2. [P2] Count scan-level exceptions as retryable failures — set result.failed > 0 in the outer catch block so scheduleOrphanRecovery retry logic triggers. 3. [P2] Persist resumed-session dedupe across recovery retries — accept resumedSessionKeys as a parameter; scheduleOrphanRecovery lifts the Set to its own scope and passes it through retries. 4. [Greptile] Use typed config accessors instead of raw structural cast for TLS check in lifecycle.ts. 5. [Greptile] Forward gateway.reload.deferralTimeoutMs to deferGatewayRestartUntilIdle in scheduleGatewaySigusr1Restart so user-configured value is not silently ignored. 6. [Greptile] Same as openclaw#4 — already addressed by the typed config fix. Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> * fix: land SIGUSR1 orphan recovery regressions (openclaw#47719) (thanks @joeykrug) * refactor: move channel messaging hooks into plugins * fix: stabilize windows parallels smoke harness * refactor(plugins): move provider onboarding auth into plugins * docs: restore onboard as canonical setup command * docs: restore onboard docs references * refactor: move channel capability diagnostics into plugins * refactor: split slack block action handling * refactor: split plugin interactive dispatch adapters * refactor: unify reply content checks * refactor: extract discord shared interactive mapper * refactor: unify telegram interactive button resolution * build: add land gate parity script * test: fix setup wizard smoke mocks * docs: sync config baseline * Status: split heartbeat summary helpers * Security: trim audit policy import surfaces * Security: lazy-load deep skill audit helpers * Security: lazy-load audit config snapshot IO * Config: keep native command defaults off heavy channel registry * Status: split lightweight gateway agent list * refactor(plugins): simplify provider auth choice metadata * test: add openshell sandbox e2e smoke * feishu: add structured card actions and interactive approval flows (openclaw#47873) * feishu: add structured card actions and interactive approval flows * feishu: address review fixes and test-gate regressions * feishu: hold inflight card dedup until completion * feishu: restore fire-and-forget bot menu handling * feishu: format card interaction helpers * Feishu: add changelog entry for card interactions * Feishu: add changelog entry for ACP session binding * build: remove land gate script * Status: lazy-load tailscale and memory scan deps * Tests: fix Feishu full registration mock * Tests: cover plugin capability matrix * Gateway: import normalizeAgentId in hooks * fix: recover bonjour advertiser from ciao announce loops * fix: preserve loopback gateway scopes for local auth * Status: lazy-load summary session helpers * Status: lazy-load security audit commands * refactor: move channel delivery and ACP seams into plugins * Security: split audit runtime surfaces * Tests: add channel actions contract helper * Tests: add channel plugin contract helper * Tests: add Slack channel contract suite * Tests: add Mattermost channel contract suite * Tests: add Telegram channel contract suite * Tests: add Discord channel contract suite * fix(session): preserve external channel route when webchat views session (openclaw#47745) When a Telegram/WhatsApp/iMessage session was viewed or messaged from the dashboard/webchat, resolveLastChannelRaw() unconditionally returned 'webchat' for any isDirectSessionKey() or isMainSessionKey() match, overwriting the persisted external delivery route. This caused subagent completion events to be delivered to the webchat/dashboard instead of the original channel (Telegram, WhatsApp, etc.), silently dropping messages for the channel user. Fix: only allow webchat to own routing when no external delivery route has been established (no persisted external lastChannel, no external channel hint in the session key). If an external route exists, webchat is treated as admin/monitoring access and must not mutate the delivery route. Updated/added tests to document the correct behaviour. Fixes openclaw#47745 * fix: address bot nit on session route preservation (openclaw#47797) (thanks @brokemac79) * Tests: add plugin contract suites * Tests: add plugin contract registry * Tests: add global plugin contract suite * Tests: add global actions contract suite * Tests: add global setup contract suite * Tests: add global status contract suite * Tests: replace local channel contracts * refactor(plugins): move onboarding auth metadata to manifests * refactor: move remaining channel seams into plugins * refactor: add plugin-owned outbound adapters * fix: scope localStorage settings key by basePath to prevent cross-deployment conflicts - Add settingsKeyForGateway() function similar to tokenSessionKeyForGateway() - Use scoped key format: openclaw.control.settings.v1:https://example.com/gateway-a - Add migration from legacy static key on load - Fixes openclaw#47481 * Tests: add provider contract suites * Tests: add provider contract registry * Tests: add global provider contract suite * Tests: add global web search contract suite * fix: stabilize ci gate * Tests: add provider registry contract suite * Tests: relax provider auth hint contract * !refactor(browser): remove Chrome extension path and add MCP doctor migration (openclaw#47893) * Browser: replace extension path with Chrome MCP * Browser: clarify relay stub and doctor checks * Docs: mark browser MCP migration as breaking * Browser: reject unsupported profile drivers * Browser: accept clawd alias on profile create * Doctor: narrow legacy browser driver migration * feishu: harden media support and align capability docs (openclaw#47968) * feishu: harden media support and action surface * feishu: format media action changes * feishu: fix review follow-ups * fix: scope Feishu target aliases to Feishu (openclaw#47968) (thanks @Takhoffman) * fix: make docs i18n use gpt-5.4 overrides * docs: regenerate zh-CN onboarding references * Tests: tighten provider wizard contracts * Tests: add plugin loader contract suite * refactor: remove dock shim and move session routing into plugins * Plugins: add provider runtime contracts * GitHub Copilot: move runtime tests to provider contracts * Z.ai: move runtime tests to provider contracts * Anthropic: move runtime tests to provider contracts * Google: move runtime tests to provider contracts * OpenAI: move runtime tests to provider contracts * Qwen Portal: move runtime tests to provider contracts * fix(core): restore outbound fallbacks and gate checks * style(core): normalize rebase fallout * fix: accept sandbox plugin id hints * Plugins: capture tool registrations in test registry * Plugins: cover Firecrawl tool ownership * Firecrawl: drop local registration contract test * Plugins: add provider catalog contracts * Plugins: narrow provider runtime contracts * refactor(plugin-sdk): use scoped core imports for bundled channels * fix: unblock ci gates * Plugins: add provider wizard contracts * fix: unblock docs and registry checks * refactor: finish plugin-owned channel runtime seams * refactor(plugin-sdk): clean shared core imports * Plugins: add provider auth contracts * Plugins: dedupe routing imports in channel adapters * Plugins: add provider discovery contracts * fix: stop bonjour before re-advertising * Plugins: extend provider discovery contracts * docs: codify macOS parallels discord smoke * refactor: move session lifecycle and outbound fallbacks into plugins * refactor(plugins): derive compat provider ids from manifests * Plugins: cover catalog discovery providers * Tests: type auth contract prompt mocks * fix: mount CLI auth dirs in docker live tests * refactor: route shared channel sdk imports through plugin seams * Plugins: add auth choice contracts * Plugins: restore routing seams and discovery fixtures * fix: harden bonjour retry recovery * Runtime: lazy-load channel runtime singletons * refactor: tighten plugin sdk channel seams * refactor: route remaining channel imports through plugin sdk * refactor(plugins): finish provider auth boundary cleanup * fix(infra): wire gaxios-fetch-compat shim to prevent node-fetch crash on Node.js 25 * fix(infra): also wire gaxios-fetch-compat shim into src/index.ts (gateway entry) * fix: keep gaxios compat off the package root (openclaw#47914) (thanks @pdd-cli) * refactor: shrink public channel plugin sdk surfaces * refactor: add private channel sdk bridges * fix: restore effective setup wizard lazy import * docs: add frontmatter to parallels discord skill * fix: retry runtime postbuild skill copy races * Gateway: lazily resolve channel runtime * Gateway: cover lazy channel runtime resolution * Plugins: add Claude marketplace registry installs (openclaw#48058) * Changelog: note Claude marketplace plugin support * Plugins: add Claude marketplace installs * E2E: cover marketplace plugin installs in Docker * UI: keep thinking helpers browser-safe * Infra: restore check after gaxios compat * Docs: refresh generated config baseline * docs: reorder unreleased changelog entries * fix: split browser-safe thinking helpers * fix(macos): restore debug build helpers (openclaw#48046) * Docs: add Claude marketplace plugin install guidance * Channels: expand contract suites * Channels: add contract surface coverage * Channels: centralize outbound payload contracts * Channels: centralize group policy contracts * Channels: centralize inbound context contracts * Tests: add contract runner * Tests: harden WhatsApp inbound contract cleanup * Tests: add extension test runner * Runtime: lazy-load Discord channel ops * Docs: use placeholders for marketplace plugin examples * Release: trim generated docs from npm pack * Runtime: lazy-load Telegram and Slack channel ops * Tests: detect changed extensions * Tests: cover changed extension detection * Docs: add extension test workflow * CI: add changed extension test lane * BlueBubbles: lazy-load channel runtime paths * Plugin SDK: restore scoped imports for bundled channels * Plugin SDK: consolidate shared channel exports * Channels: fix surface contract plugin lookup * Status: stabilize startup memory probes * Media: avoid slow auth misses in auto-detect * Tests: scope Codex bundle loader fixture * Tests: isolate bundle surface fixtures * feat(telegram): add configurable silent error replies (openclaw#19776) Port and complete openclaw#19776 on top of the current Telegram extension layout. Adds a default-off `channels.telegram.silentErrorReplies` setting. When enabled, Telegram bot replies marked as errors are delivered silently across the regular bot reply flow, native/slash command replies, and fallback sends. Thanks @auspic7 Co-authored-by: Myeongwon Choi <[email protected]> Co-authored-by: ImLukeF <[email protected]> * fix(ui): auto load Usage tab data on navigation * fix(telegram): keep silent error fallback replies quiet * test(gateway): restore agent request route mock * Cron: isolate active-model delivery tests * Tests: align media auth fixture with selection checks * Plugins: preserve lazy runtime provider resolution * Bootstrap: report nested entry import misses * fix(channels): parse bundled targets without plugin registry * test(telegram): cover shared parsing without registry * Plugin SDK: split setup and sandbox subpaths * Providers: centralize setup defaults and helper boundaries * Plugins: decouple bundled web search discovery * Plugin SDK: update entrypoint metadata * Secrets: honor caller env during runtime validation * Tests: align Docker cache checks with non-root images * Plugin SDK: keep root alias reflection lazy * Providers: scope compat resolution to owning plugins * Plugin SDK: add narrow setup subpaths * Plugin SDK: update entrypoint metadata * fix(slack): harden bolt import interop (openclaw#45953) * fix(slack): harden bolt import interop * fix(slack): simplify bolt interop resolver * fix(slack): harden startup bolt interop * fix(slack): place changelog entry at section end --------- Co-authored-by: Ubuntu <[email protected]> Co-authored-by: Altay <[email protected]> * Tests: fix green check typing regressions * Plugins: avoid booting bundled providers for catalog hooks * fix: bypass telegram runtime proxy during health checks * fix: align telegram probe test mock * test: remove stale synology zod mock * fix(android): reduce chat recomposition churn * fix(android): preserve chat message identity on refresh * fix(android): shrink chat image attachments * Browser: support non-Chrome existing-session profiles via userDataDir (openclaw#48170) Merged via squash. Prepared head SHA: e490035 Co-authored-by: velvet-shark <[email protected]> Co-authored-by: velvet-shark <[email protected]> Reviewed-by: @velvet-shark * fix(local-storage): improve VITEST environment check for localStorage access * fix: normalize discord commands allowFrom auth * test: update discord subagent hook mocks * test: mock telegram native command reply pipeline * fix(android): lazy-init node runtime after onboarding * docs(config): refresh generated baseline * Plugins: share channel plugin id resolution * Gateway: defer full channel plugins until after listen * Gateway: gate deferred channel startup behind opt-in * Docs: document deferred channel startup opt-in * feat(skills): preserve all skills in prompt via compact fallback before dropping (openclaw#47553) * feat(skills): add compact format fallback for skill catalog truncation When the full-format skill catalog exceeds the character budget, applySkillsPromptLimits now tries a compact format (name + location only, no description) before binary-searching for the largest fitting prefix. This preserves full model awareness of registered skills in the common overflow case. Three-tier strategy: 1. Full format fits → use as-is 2. Compact format fits → switch to compact, keep all skills 3. Compact still too large → binary search largest compact prefix Other changes: - escapeXml() utility for safe XML attribute values - formatSkillsCompact() emits same XML structure minus <description> - Compact char-budget check reserves 150 chars for the warning line the caller prepends, preventing prompt overflow at the boundary - 13 tests covering all tiers, edge cases, and budget reservation - docs/.generated/config-baseline.json: fix pre-existing oxfmt issue * docs: document compact skill prompt fallback --------- Co-authored-by: Frank Yang <[email protected]> * Gateway: simplify startup and stabilize mock responses tests * test: fix stale web search and boot-md contracts * Gateway tests: centralize mock responses provider setup * Gateway tests: share ordered client teardown helper * Infra: ignore ciao probing cancellations * Docs: repair unreleased changelog attribution * Docs: normalize unreleased changelog refs * Channels: ignore enabled-only disabled plugin config * perf: reduce status json startup memory * perf: lazy-load status route startup helpers * Plugins: stage local bundled runtime tree * Build: share root dist chunks across tsdown entries * fix(logging): make logger import browser-safe * fix(changelog): add entry for Control UI logger import fix (openclaw#48469) * fix(changelog): note Control UI logger import fix * fix(changelog): attribute Control UI logger fix entry * fix(changelog): credit original Control UI fix author * Plugins: remove public extension-api surface (openclaw#48462) * Plugins: remove public extension-api surface * Plugins: fix loader setup routing follow-ups * CI: ignore non-extension helper dirs in extension-fast * Docs: note extension-api removal as breaking * fix(ui): language dropdown selection not persisting after refresh (openclaw#48019) Merged via squash. Prepared head SHA: 06c8258 Co-authored-by: git-jxj <[email protected]> Co-authored-by: altaywtf <[email protected]> Reviewed-by: @altaywtf * fix(plugins): late-binding subagent runtime for non-gateway load paths (openclaw#46648) Merged via squash. Prepared head SHA: 4474265 Co-authored-by: jalehman <[email protected]> Co-authored-by: jalehman <[email protected]> Reviewed-by: @jalehman * fix: enable auto-scroll during assistant response streaming Fix auto-scroll behavior when AI assistant streams responses in the web UI. Previously, the viewport would remain at the sent message position and users had to manually click a badge to see streaming responses. Fixes openclaw#14959 Changes: - Reset chat scroll state before sending message to ensure viewport readiness - Force scroll to bottom after message send to position viewport correctly - Detect streaming start (chatStream: null -> string) and trigger auto-scroll - Ensure smooth scroll-following during entire streaming response Co-Authored-By: Claude Opus 4.6 <[email protected]> * fix(ui): align chatStream lifecycle type with nullable state * fix(whatsapp): restore implicit reply mentions for LID identities (openclaw#48494) Threads selfLid from the Baileys socket through the inbound WhatsApp pipeline and adds LID-format matching to the implicit mention check in group gating, so reply-to-bot detection works when WhatsApp sends the quoted sender in @lid format. Also fixes the device-suffix stripping regex (was a silent no-op). Closes openclaw#23029 Co-authored-by: sparkyrider <[email protected]> Reviewed-by: @ademczuk * fix(compaction): stabilize toolResult trim/prune flow in safeguard (openclaw#44133) Merged via squash. Prepared head SHA: ec789c6 Co-authored-by: SayrWolfridge <[email protected]> Co-authored-by: jalehman <[email protected]> Reviewed-by: @jalehman * Fix launcher startup regressions (openclaw#48501) * Fix launcher startup regressions * Fix CI follow-up regressions * Fix review follow-ups * Fix workflow audit shell inputs * Handle require resolve gaxios misses * fix: remove orphaned tool_result blocks during compaction (openclaw#15691) (openclaw#16095) Merged via squash. Prepared head SHA: b772432 Co-authored-by: claw-sylphx <[email protected]> Co-authored-by: jalehman <[email protected]> Reviewed-by: @jalehman * docs: rename onboarding user-facing wizard copy Co-authored-by: Tak <[email protected]> * fix(plugins): keep built plugin loading on one module graph (openclaw#48595) * Plugins: stabilize global catalog contracts * Channels: add global threading and directory contracts * Tests: improve extension runner discovery * CI: run global contract lane * Plugins: speed up auth-choice contracts * Plugins: fix catalog contract mocks * refactor: move provider catalogs into extensions * refactor: route bundled channel setup helpers through private sdk bridges * test: fix check contract type drift * Tests: lock plugin slash commands to one runtime graph * Tests: cover Discord provider plugin registry * Tests: pin loader command activation semantics * Tests: cover Telegram plugin auth on real registry * refactor(slack): share setup helpers * refactor(whatsapp): reuse shared normalize helpers * Tlon: lazy-load channel runtime paths * Tests: document Discord plugin auth gating * feat(plugins): add speech provider registration * docs(plugins): document capability ownership model * fix: detect Ollama "prompt too long" as context overflow error (openclaw#34019) Merged via squash. Prepared head SHA: 825a402 Co-authored-by: lishuaigit <[email protected]> Co-authored-by: jalehman <[email protected]> Reviewed-by: @jalehman * agent: preemptive context overflow detection during tool loops (openclaw#29371) Merged via squash. Prepared head SHA: 19661b8 Co-authored-by: keshav55 <[email protected]> Co-authored-by: jalehman <[email protected]> Reviewed-by: @jalehman --------- Co-authored-by: Peter Steinberger <[email protected]> Co-authored-by: MoerAI <[email protected]> Co-authored-by: Joey Krug <[email protected]> Co-authored-by: bot_apk <[email protected]> Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: Vincent Koc <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> Co-authored-by: brokemac79 <[email protected]> Co-authored-by: ObitaBot <[email protected]> Co-authored-by: Prompt Driven <[email protected]> Co-authored-by: Nimrod Gutman <[email protected]> Co-authored-by: Gustavo Madeira Santana <[email protected]> Co-authored-by: Myeongwon Choi <[email protected]> Co-authored-by: Myeongwon Choi <[email protected]> Co-authored-by: ImLukeF <[email protected]> Co-authored-by: 郑耀宏 <[email protected]> Co-authored-by: Ayaan Zaidi <[email protected]> Co-authored-by: huntharo <[email protected]> Co-authored-by: Yauheni Shauchenka <[email protected]> Co-authored-by: Ubuntu <[email protected]> Co-authored-by: Altay <[email protected]> Co-authored-by: Radek Sienkiewicz <[email protected]> Co-authored-by: velvet-shark <[email protected]> Co-authored-by: Val Alexander <[email protected]> Co-authored-by: Hung-Che Lo <[email protected]> Co-authored-by: Frank Yang <[email protected]> Co-authored-by: git-jxj <[email protected]> Co-authored-by: git-jxj <[email protected]> Co-authored-by: altaywtf <[email protected]> Co-authored-by: Josh Lehman <[email protected]> Co-authored-by: jalehman <[email protected]> Co-authored-by: Jaewon Hwang <[email protected]> Co-authored-by: Claude Opus 4.6 <[email protected]> Co-authored-by: sparkyrider <[email protected]> Co-authored-by: sparkyrider <[email protected]> Co-authored-by: Sayr Wolfridge <[email protected]> Co-authored-by: SayrWolfridge <[email protected]> Co-authored-by: Clayton Shaw <[email protected]> Co-authored-by: claw-sylphx <[email protected]> Co-authored-by: Tak <[email protected]> Co-authored-by: lishuaigit <[email protected]> Co-authored-by: lishuaigit <[email protected]> Co-authored-by: Keshav Rao <[email protected]> Co-authored-by: keshav55 <[email protected]>

…#48595)

…#48595) (cherry picked from commit 94c27f3)

…#48595)

openclaw-barnacle bot added scripts Repository scripts size: M maintainer Maintainer-authored PR labels Mar 17, 2026

greptile-apps bot reviewed Mar 17, 2026

View reviewed changes

chatgpt-codex-connector bot reviewed Mar 17, 2026

View reviewed changes

fix(plugins): prefer native dist modules in plugin loaders

2d8d178

huntharo force-pushed the codex/fix-duplicate-load-of-files branch from e3720e0 to 9bf69b3 Compare March 17, 2026 00:57

huntharo added 2 commits March 16, 2026 20:58

fix(plugins): unify built plugin runtime graph

ec31eae

Build: type tsdown config input options

18baf0a

huntharo force-pushed the codex/fix-duplicate-load-of-files branch from 9bf69b3 to 18baf0a Compare March 17, 2026 00:58

huntharo merged commit 94c27f3 into openclaw:main Mar 17, 2026
25 of 33 checks passed

huntharo deleted the codex/fix-duplicate-load-of-files branch March 17, 2026 00:59

chatgpt-codex-connector bot reviewed Mar 17, 2026

View reviewed changes

github-actions bot mentioned this pull request Mar 17, 2026

📡 Upstream Digest — 2026-03-17 01:22 UTC curtismercier/openclaw-mods#284

Open

vincentkoc pushed a commit to vincentkoc/openclaw that referenced this pull request Mar 17, 2026

fix(plugins): keep built plugin loading on one module graph (openclaw…

508dca3

…#48595)

Takhoffman mentioned this pull request Mar 17, 2026

CI: add built plugin singleton smoke #48710

Merged

20 tasks

hqwuzhaoyi pushed a commit to hqwuzhaoyi/openclaw that referenced this pull request Mar 17, 2026

fix(plugins): keep built plugin loading on one module graph (openclaw…

f76c7f3

…#48595)

huntharo mentioned this pull request Mar 17, 2026

CI: guard gateway watch against duplicate runtime regressions #49048

Merged

20 tasks

This was referenced Mar 17, 2026

Fix/acpx runtime skill copy AcorpBG/openclaw#16

Closed

Fix/dist-runtime skill copy instead of symlink #49198

Open

nikolaisid pushed a commit to nikolaisid/openclaw that referenced this pull request Mar 18, 2026

fix(plugins): keep built plugin loading on one module graph (openclaw…

02fb39c

…#48595)

zxkane mentioned this pull request Mar 18, 2026

fix(bedrock): support Application Inference Profile ARNs as model identifiers #48163

Open

alexey-pelykh mentioned this pull request Mar 23, 2026

Cherry-pick: Build system and dependencies (1/2) (50 commits) remoteclaw/remoteclaw#1906

Closed

alexey-pelykh pushed a commit to remoteclaw/remoteclaw that referenced this pull request Mar 25, 2026

fix(plugins): keep built plugin loading on one module graph (openclaw…

fef161c

…#48595) (cherry picked from commit 94c27f3)

sbezludny pushed a commit to sbezludny/openclaw that referenced this pull request Mar 27, 2026

fix(plugins): keep built plugin loading on one module graph (openclaw…

5a2330f

…#48595)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(plugins): keep built plugin loading on one module graph#48595

fix(plugins): keep built plugin loading on one module graph#48595
huntharo merged 3 commits intoopenclaw:mainfrom
huntharo:codex/fix-duplicate-load-of-files

huntharo commented Mar 17, 2026

Uh oh!

greptile-apps bot commented Mar 17, 2026

Uh oh!

greptile-apps bot Mar 17, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

chatgpt-codex-connector bot Mar 17, 2026

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

chatgpt-codex-connector bot Mar 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

huntharo commented Mar 17, 2026

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

User-visible / Behavior Changes

Security Impact (required)

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification (required)

Review Conversations

Compatibility / Migration

Failure Recovery (if this breaks)

Risks and Mitigations

Uh oh!

greptile-apps bot commented Mar 17, 2026

Greptile Summary

Confidence Score: 4/5

Uh oh!

greptile-apps bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant