Plugins: add Claude marketplace registry installs by vincentkoc · Pull Request #48058 · openclaw/openclaw

vincentkoc · 2026-03-16T08:45:51Z

Summary

Problem: OpenClaw could install Claude-compatible plugin bundles, but it could not resolve or sync plugins from Claude marketplace registries.
Why it matters: Claude users copy commands like plugin@marketplace, and those installs/update flows were dead in OpenClaw.
What changed: added marketplace registry resolution from Claude's local registry, plugin@marketplace installs, marketplace listing, persisted install metadata, update support, and Docker E2E coverage.
What did NOT change (scope boundary): this does not add a new hosted OpenClaw registry or change normal npm/bundled plugin install precedence outside the new marketplace path.

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Closes #
Related #

User-visible / Behavior Changes

openclaw plugins install superpowers@claude-plugins-official now resolves via Claude marketplace registry metadata.
openclaw plugins marketplace list <marketplace> can list Claude marketplace entries.
Marketplace installs are recorded as source: "marketplace" and can be updated via openclaw plugins update.

Security Impact (required)

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

This adds a new plugin install source that can read Claude marketplace registry state from ~/.claude/plugins/known_marketplaces.json and fetch marketplace sources over git when needed. Risk is bounded by reusing the existing plugin install path, persisting explicit install metadata, and keeping Docker E2E coverage over both shorthand and explicit marketplace flows.

Repro + Verification

Environment

OS: macOS host, Docker Desktop Linux container
Runtime/container: Node 24 / pnpm, repo Docker E2E image
Model/provider: N/A
Integration/channel (if any): Claude marketplace plugin registry compatibility
Relevant config (redacted): temporary HOME with fixture Claude registry; local ~/.claude/plugins/known_marketplaces.json for live manual validation

Steps

Seed or use a Claude marketplace registry entry.
Run openclaw plugins marketplace list <marketplace>.
Run openclaw plugins install <plugin>@<marketplace>.
Run openclaw plugins update <plugin> after changing the marketplace source.

Expected

Marketplace plugins list, install, persist, and update through the standard plugin flow.

Actual

Verified locally; commands succeed in both focused tests and Docker E2E.

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: pnpm test -- src/plugins/marketplace.test.ts src/plugins/update.test.ts; pnpm test:docker:plugins; docker build -f scripts/e2e/Dockerfile.qr-import .; live shorthand installs for superpowers@claude-plugins-official and semgrep@claude-plugins-official.
Edge cases checked: local fixture marketplace, explicit --marketplace, shorthand plugin@marketplace, persisted install metadata, marketplace update flow, Docker appuser ownership/runtime.
What you did not verify: full hosted registry UX beyond Claude-compatible local registry metadata; CI on GitHub runners.

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 avoid marketplace shorthand/install paths and use existing npm/local install flows.
Files/config to restore: plugin install metadata in ~/.openclaw/openclaw.json for affected installs.
Known bad symptoms reviewers should watch for: marketplace list/install JSON output regressions, failed shorthand resolution, incorrect install source metadata, Docker permission failures under appuser.

Risks and Mitigations

Risk: marketplace metadata can point at git or path sources that behave differently from npm installs.
- Mitigation: install records persist the resolved marketplace source/plugin tuple, updates reuse that metadata, and Docker E2E exercises install plus update end to end.

greptile-apps · 2026-03-16T08:51:06Z

Greptile Summary

This PR adds Claude marketplace registry support to OpenClaw's plugin system: plugin@marketplace shorthand installs, plugins marketplace list, persisted source: "marketplace" install records, and update support, backed by Docker E2E coverage.

The feature is well-structured overall and follows existing plugin install patterns. A few issues are worth addressing before merge:

Security — absolute path bypass: Marketplace plugin entries using an absolute path source skip ensureInsideMarketplaceRoot entirely. Since marketplace manifests can originate from remote git repos, a malicious manifest could point to any host path (e.g. "/etc/ssh/id_rsa"). Relative paths should be enforced for all path-kind marketplace entries.
Logic bug — git-subdir subdirectory path dropped: marketplaceEntrySourceToInput omits the required path field for git-subdir sources. When a known_marketplaces.json entry uses git-subdir, the recursive loadMarketplace call loses the subdir and the manifest lookup silently fails at the repo root.
Style — git SSH URLs fall through to local-path handling: Bare git@... strings passed to normalizeEntrySource are classified as kind: "path" rather than kind: "git", relying on a multi-step fallback in loadMarketplace to ultimately clone them. Adding an explicit isGitUrl branch would make the intent clear.

Confidence Score: 2/5

Not safe to merge until the absolute-path security bypass in marketplace plugin entry resolution is addressed.
The feature design and integration are sound, and update/CLI wiring look correct. However the absolute-path bypass in resolveMarketplaceEntryInstallPath is a meaningful security issue for a code path that fetches and executes manifests from remote git sources. The git-subdir serialization bug would silently break a supported source kind. These should be fixed before shipping.
src/plugins/marketplace.ts — absolute path bypass and git-subdir serialization bug both live here.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: src/plugins/marketplace.ts
Line: 494-496

Comment:
**Absolute paths bypass marketplace root confinement**

Plugin entries with `kind: "path"` that contain an absolute path skip the `ensureInsideMarketplaceRoot` check entirely. Because marketplace manifests can come from remotely-cloned git repos, a malicious (or compromised) marketplace could include `"source": "/etc/ssh/id_rsa"` or any other sensitive path on the host, and `installPluginFromPath` would be invoked with that unrestricted path.

Marketplace plugin paths should always be relative to the marketplace root. Consider rejecting absolute paths:

```suggestion
    const resolved = path.isAbsolute(params.source.path)
      ? ({ ok: false as const, error: `absolute plugin paths are not permitted in marketplace entries: ${params.source.path}` })
      : ensureInsideMarketplaceRoot(params.marketplaceRootDir, params.source.path);
```

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

---

This is a comment left during a code review.
Path: src/plugins/marketplace.ts
Line: 203-204

Comment:
**`git-subdir` subdirectory path is silently dropped during serialization**

`marketplaceEntrySourceToInput` returns only the URL for `git-subdir` sources, omitting the required `path` field. This serialized string is used when `loadMarketplace` resolves a `known_marketplaces.json` entry whose source is `git-subdir` (via the recursive call on ~line 432):

```typescript
return await loadMarketplace({
  source: marketplaceEntrySourceToInput(normalizedSource.source), // path dropped here
  ...
});
```

`loadMarketplace` will then clone the repo and look for a marketplace manifest at the repo root rather than at the intended subdirectory, producing a silent "manifest not found" failure.

The `git` case has the same omission, though `git` sources use `path` as an optional subdirectory for the *plugin* inside the repo (resolved later in `resolveMarketplaceEntryInstallPath`), so the impact there is different. For `git-subdir`, the `path` field is always required and defines which directory *is* the marketplace.

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

---

This is a comment left during a code review.
Path: src/plugins/marketplace.ts
Line: 108-112

Comment:
**Git SSH URL strings are silently treated as local paths**

`normalizeEntrySource` handles bare strings with only two cases: HTTP URLs become `{ kind: "url" }` and everything else becomes `{ kind: "path" }`. A git SSH URL like `[email protected]:owner/repo.git` stored in `known_marketplaces.json` as a plain string would therefore be resolved as a local path, causing `resolveLocalMarketplaceSource` to fail (path doesn't exist) and then falling through to `cloneMarketplaceRepo` which happens to re-parse the string via `normalizeGitCloneSource`. The feature works, but the flow is unintuitive and depends on the fallback chain in `loadMarketplace`. Adding an explicit `isGitUrl` branch here would make the behaviour intentional and easier to reason about:

```suggestion
  if (isHttpUrl(trimmed)) {
    return { ok: true, source: { kind: "url", url: trimmed } };
  }
  if (isGitUrl(trimmed) || looksLikeGitHubRepoShorthand(trimmed)) {
    return { ok: true, source: { kind: "git", url: trimmed } };
  }
  return { ok: true, source: { kind: "path", path: trimmed } };
```

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

_{Last reviewed commit: 0cc27bf}

greptile-apps · 2026-03-16T08:51:10Z

src/plugins/marketplace.ts

+  }
+
+  const local = await resolveLocalMarketplaceSource(params.source);


Absolute paths bypass marketplace root confinement

Plugin entries with kind: "path" that contain an absolute path skip the ensureInsideMarketplaceRoot check entirely. Because marketplace manifests can come from remotely-cloned git repos, a malicious (or compromised) marketplace could include "source": "/etc/ssh/id_rsa" or any other sensitive path on the host, and installPluginFromPath would be invoked with that unrestricted path.

Marketplace plugin paths should always be relative to the marketplace root. Consider rejecting absolute paths:

Suggested change

}

const local = await resolveLocalMarketplaceSource(params.source);

const resolved = path.isAbsolute(params.source.path)

? ({ ok: false as const, error: `absolute plugin paths are not permitted in marketplace entries: ${params.source.path}` })

: ensureInsideMarketplaceRoot(params.marketplaceRootDir, params.source.path);

Prompt To Fix With AI

This is a comment left during a code review. Path: src/plugins/marketplace.ts Line: 494-496 Comment: **Absolute paths bypass marketplace root confinement** Plugin entries with `kind: "path"` that contain an absolute path skip the `ensureInsideMarketplaceRoot` check entirely. Because marketplace manifests can come from remotely-cloned git repos, a malicious (or compromised) marketplace could include `"source": "/etc/ssh/id_rsa"` or any other sensitive path on the host, and `installPluginFromPath` would be invoked with that unrestricted path. Marketplace plugin paths should always be relative to the marketplace root. Consider rejecting absolute paths: ```suggestion const resolved = path.isAbsolute(params.source.path) ? ({ ok: false as const, error: `absolute plugin paths are not permitted in marketplace entries: ${params.source.path}` }) : ensureInsideMarketplaceRoot(params.marketplaceRootDir, params.source.path); ``` How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-03-16T08:51:10Z

src/plugins/marketplace.ts

+        kind: "git-subdir",
+        url,


git-subdir subdirectory path is silently dropped during serialization

marketplaceEntrySourceToInput returns only the URL for git-subdir sources, omitting the required path field. This serialized string is used when loadMarketplace resolves a known_marketplaces.json entry whose source is git-subdir (via the recursive call on ~line 432):

return await loadMarketplace({ source: marketplaceEntrySourceToInput(normalizedSource.source), // path dropped here ... });

loadMarketplace will then clone the repo and look for a marketplace manifest at the repo root rather than at the intended subdirectory, producing a silent "manifest not found" failure.

The git case has the same omission, though git sources use path as an optional subdirectory for the plugin inside the repo (resolved later in resolveMarketplaceEntryInstallPath), so the impact there is different. For git-subdir, the path field is always required and defines which directory is the marketplace.

Prompt To Fix With AI

This is a comment left during a code review. Path: src/plugins/marketplace.ts Line: 203-204 Comment: **`git-subdir` subdirectory path is silently dropped during serialization** `marketplaceEntrySourceToInput` returns only the URL for `git-subdir` sources, omitting the required `path` field. This serialized string is used when `loadMarketplace` resolves a `known_marketplaces.json` entry whose source is `git-subdir` (via the recursive call on ~line 432): ```typescript return await loadMarketplace({ source: marketplaceEntrySourceToInput(normalizedSource.source), // path dropped here ... }); ``` `loadMarketplace` will then clone the repo and look for a marketplace manifest at the repo root rather than at the intended subdirectory, producing a silent "manifest not found" failure. The `git` case has the same omission, though `git` sources use `path` as an optional subdirectory for the *plugin* inside the repo (resolved later in `resolveMarketplaceEntryInstallPath`), so the impact there is different. For `git-subdir`, the `path` field is always required and defines which directory *is* the marketplace. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-03-16T08:51:12Z

src/plugins/marketplace.ts

+  const trimmed = value.trim();
+  const hashIndex = trimmed.lastIndexOf("#");
+  if (hashIndex <= 0 || hashIndex >= trimmed.length - 1) {
+    return { base: trimmed };
+  }


Git SSH URL strings are silently treated as local paths

normalizeEntrySource handles bare strings with only two cases: HTTP URLs become { kind: "url" } and everything else becomes { kind: "path" }. A git SSH URL like [email protected]:owner/repo.git stored in known_marketplaces.json as a plain string would therefore be resolved as a local path, causing resolveLocalMarketplaceSource to fail (path doesn't exist) and then falling through to cloneMarketplaceRepo which happens to re-parse the string via normalizeGitCloneSource. The feature works, but the flow is unintuitive and depends on the fallback chain in loadMarketplace. Adding an explicit isGitUrl branch here would make the behaviour intentional and easier to reason about:

Suggested change

const trimmed = value.trim();

const hashIndex = trimmed.lastIndexOf("#");

if (hashIndex <= 0 || hashIndex >= trimmed.length - 1) {

return { base: trimmed };

}

if (isHttpUrl(trimmed)) {

return { ok: true, source: { kind: "url", url: trimmed } };

}

if (isGitUrl(trimmed) || looksLikeGitHubRepoShorthand(trimmed)) {

return { ok: true, source: { kind: "git", url: trimmed } };

}

return { ok: true, source: { kind: "path", path: trimmed } };

Prompt To Fix With AI

This is a comment left during a code review. Path: src/plugins/marketplace.ts Line: 108-112 Comment: **Git SSH URL strings are silently treated as local paths** `normalizeEntrySource` handles bare strings with only two cases: HTTP URLs become `{ kind: "url" }` and everything else becomes `{ kind: "path" }`. A git SSH URL like `[email protected]:owner/repo.git` stored in `known_marketplaces.json` as a plain string would therefore be resolved as a local path, causing `resolveLocalMarketplaceSource` to fail (path doesn't exist) and then falling through to `cloneMarketplaceRepo` which happens to re-parse the string via `normalizeGitCloneSource`. The feature works, but the flow is unintuitive and depends on the fallback chain in `loadMarketplace`. Adding an explicit `isGitUrl` branch here would make the behaviour intentional and easier to reason about: ```suggestion if (isHttpUrl(trimmed)) { return { ok: true, source: { kind: "url", url: trimmed } }; } if (isGitUrl(trimmed) || looksLikeGitHubRepoShorthand(trimmed)) { return { ok: true, source: { kind: "git", url: trimmed } }; } return { ok: true, source: { kind: "path", path: trimmed } }; ``` 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: 0cc27bf2e5

ℹ️ 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-16T08:51:37Z

src/cli/plugins-cli.ts

+    .action(async (source: string, opts: PluginMarketplaceListOptions) => {
+      const result = await listMarketplacePlugins({
+        marketplace: source,
+        logger: createPluginInstallLogger(),


Avoid logging progress in JSON marketplace list mode

When plugins marketplace list --json is used with a non-local source, this call always passes createPluginInstallLogger(), and cloneMarketplaceRepo emits info messages before the JSON payload. That makes stdout non-JSON and breaks scripts that parse the command output. Please suppress the logger (or route progress to stderr) when --json is set.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-03-16T08:51:37Z

src/plugins/marketplace.ts

+      return `${source.repo}${source.ref ? `#${source.ref}` : ""}`;
+    case "git":
+      return `${source.url}${source.ref ? `#${source.ref}` : ""}`;
+    case "git-subdir":
+      return `${source.url}${source.ref ? `#${source.ref}` : ""}`;


Preserve marketplace subdir metadata when resolving sources

This conversion drops path information for github/git/git-subdir sources, so a known marketplace that is declared in a repository subdirectory is reloaded from the repo root instead. In that case loadMarketplace cannot find the manifest after following known_marketplaces.json (especially when installLocation is absent/stale), so marketplace list/install/update fails even though the source metadata was valid.

Useful? React with 👍 / 👎.

@pdd-cli

* main: (340 commits) fix: split browser-safe thinking helpers docs: reorder unreleased changelog entries Docs: refresh generated config baseline Infra: restore check after gaxios compat UI: keep thinking helpers browser-safe Plugins: add Claude marketplace registry installs (openclaw#48058) Gateway: cover lazy channel runtime resolution Gateway: lazily resolve channel runtime fix: retry runtime postbuild skill copy races docs: add frontmatter to parallels discord skill fix: restore effective setup wizard lazy import refactor: add private channel sdk bridges refactor: shrink public channel plugin sdk surfaces fix: keep gaxios compat off the package root (openclaw#47914) (thanks @pdd-cli) fix(infra): also wire gaxios-fetch-compat shim into src/index.ts (gateway entry) fix(infra): wire gaxios-fetch-compat shim to prevent node-fetch crash on Node.js 25 refactor(plugins): finish provider auth boundary cleanup refactor: route remaining channel imports through plugin sdk refactor: tighten plugin sdk channel seams Runtime: lazy-load channel runtime singletons ...

* Changelog: note Claude marketplace plugin support * Plugins: add Claude marketplace installs * E2E: cover marketplace plugin installs in Docker

@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]>

* Changelog: note Claude marketplace plugin support * Plugins: add Claude marketplace installs * E2E: cover marketplace plugin installs in Docker

vincentkoc added 3 commits March 16, 2026 01:40

Changelog: note Claude marketplace plugin support

45fb578

Plugins: add Claude marketplace installs

8241311

E2E: cover marketplace plugin installs in Docker

0cc27bf

vincentkoc self-assigned this Mar 16, 2026

openclaw-barnacle bot added cli CLI command changes scripts Repository scripts docker Docker and sandbox tooling labels Mar 16, 2026

vincentkoc merged commit ff2e864 into main Mar 16, 2026
12 checks passed

vincentkoc deleted the vincentkoc-code/claude-marketplace-sync branch March 16, 2026 08:46

openclaw-barnacle bot added size: XL maintainer Maintainer-authored PR labels Mar 16, 2026

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

📡 Upstream Digest — 2026-03-16 08:47 UTC curtismercier/openclaw-mods#278

Open

greptile-apps bot reviewed Mar 16, 2026

View reviewed changes

chatgpt-codex-connector bot reviewed Mar 16, 2026

View reviewed changes

vincentkoc mentioned this pull request Mar 17, 2026

Agents: run bundle MCP tools in embedded Pi #48611

Merged

20 tasks

bm-clawd mentioned this pull request Mar 25, 2026

Create OpenClaw plugin for Basic Memory and publish to Claude marketplace registry basicmachines-co/openclaw-basic-memory#36

Open

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Plugins: add Claude marketplace registry installs#48058

Plugins: add Claude marketplace registry installs#48058
vincentkoc merged 3 commits intomainfrom
vincentkoc-code/claude-marketplace-sync

vincentkoc commented Mar 16, 2026

Uh oh!

Uh oh!

greptile-apps bot commented Mar 16, 2026

Uh oh!

greptile-apps bot Mar 16, 2026

Uh oh!

greptile-apps bot Mar 16, 2026

Uh oh!

greptile-apps bot Mar 16, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

chatgpt-codex-connector bot Mar 16, 2026

Uh oh!

chatgpt-codex-connector bot Mar 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

		}

		const local = await resolveLocalMarketplaceSource(params.source);

Uh oh!

Conversation

vincentkoc commented Mar 16, 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!

Uh oh!

greptile-apps bot commented Mar 16, 2026

Greptile Summary

Confidence Score: 2/5

Uh oh!

greptile-apps bot Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Mar 16, 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 16, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector bot Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant