Plugins: remove public extension-api surface by Takhoffman · Pull Request #48462 · openclaw/openclaw

Takhoffman · 2026-03-16T19:41:43Z

Summary

remove the public openclaw/extension-api export, build entry, loader aliasing, and type shim
move host agent/session operations behind injected api.runtime.agent
migrate bundled llm-task and voice-call consumers to the plugin runtime boundary

Verification

pnpm build
pnpm check
pnpm exec vitest run --config vitest.config.ts src/plugins/runtime/index.test.ts src/plugin-sdk/subpaths.test.ts src/plugins/loader.test.ts extensions/llm-task/src/llm-task-tool.test.ts extensions/voice-call/src/runtime.test.ts

greptile-apps · 2026-03-16T19:44:49Z

Greptile Summary

This PR cleanly removes the openclaw/extension-api public export surface — deleting src/extensionAPI.ts, the ./extension-api package.json export, tsconfig.json path alias, vitest alias, tsdown build entry, and knip entry. Host agent/session operations are moved from a dynamic file-system-crawling loader (loadCoreAgentDeps) into an injected api.runtime.agent dependency, wired via a new createRuntimeAgent() factory. Both llm-task and voice-call consumers are correctly migrated to the new boundary.

Key observations:

The core-bridge.ts removal is a significant improvement: 140+ lines of fragile runtime path-walking + pathToFileURL dynamic import are replaced by a single type alias.
The migration to injected agentRuntime is consistent and well-tested.
One unrelated logic change in shouldLoadChannelPluginInSetupRuntime (src/plugins/loader.ts) adds a fast-path that returns true when a channel key merely exists in cfg.channels, bypassing the credential/config validation inside isChannelConfigured. This can cause plugins to skip setup mode for partially-configured channels (e.g. { twilio: {} }), which is a behavioral regression not described in the PR.
SessionEntry.sessionFile?: string is added to the type in response-generator.ts but is never stored, making the field perpetually undefined in the persisted session store.

Confidence Score: 3/5

Mostly safe to merge for the stated extension-API removal goal, but contains a bundled logic regression in channel plugin setup-mode loading.
The extension-API removal and dependency-injection migration are clean and well-covered by the accompanying tests. However, shouldLoadChannelPluginInSetupRuntime contains a short-circuit that bypasses isChannelConfigured's credential validation, which is unrelated to the PR's purpose and can silently prevent channels from receiving the setup runtime when their config block is present but unconfigured. This warrants attention before merge.
src/plugins/loader.ts — the shouldLoadChannelPluginInSetupRuntime change; extensions/voice-call/src/response-generator.ts — unused sessionFile field on SessionEntry

Prompt To Fix All With AI

This is a comment left during a code review.
Path: src/plugins/loader.ts
Line: 442-453

Comment:
**Fast-path short-circuits `isChannelConfigured` credential checks**

The new fast-path uses `Object.hasOwn(configuredChannels, channelId)` to immediately return `true` (treating the channel as configured) when a channel key is merely present in `cfg.channels`. However, `isChannelConfigured` does substantially more: it validates actual credentials — checking env vars (`envAny`, `envAll`), non-empty string keys, and `hasMeaningfulChannelConfig`. A channel entry such as `{ twilio: {} }` (key present but no credentials) would be caught by `isChannelConfigured` (returns `false`), but the new fast-path will short-circuit and return `true`, preventing the plugin from loading in setup mode.

This means users with an empty or partially-configured channel block in their config will no longer see the setup runtime for that channel plugin, even though the channel isn't actually usable.

This behavior change appears unrelated to the stated PR goal (removing the `extension-api` export surface). Consider removing the fast-path or, if the intent is a real optimization, gate it with a value-presence check rather than key presence:

```suggestion
  const configuredChannels = params.cfg.channels;
  return !params.manifestChannels.some((channelId) => {
    return isChannelConfigured(params.cfg, channelId, params.env);
  });
```

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

---

This is a comment left during a code review.
Path: extensions/voice-call/src/response-generator.ts
Line: 32-36

Comment:
**`sessionFile` field added to `SessionEntry` but never persisted**

The `sessionFile?: string` field is added to `SessionEntry`, which is used to type objects read from and written to the session store. However, `sessionFile` is never assigned on the `sessionEntry` object at creation time (lines 70–76) and is never stored back via `saveSessionStore`. The value is only computed locally from `agentRuntime.session.resolveSessionFilePath(...)`. As a result, this field will always be `undefined` when reading back an existing session entry from the store, and it's never written.

If the intent is to cache the file path in the store to support `resolveSessionFilePath` (which appears to take `sessionEntry` as its second arg), the field should be populated before saving. Otherwise, the type addition is misleading and should be removed.

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

_{Last reviewed commit: 27ba829}

src/plugins/loader.ts

extensions/voice-call/src/response-generator.ts

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 27ba829e5f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

src/plugins/loader.ts

aisle-research-bot · 2026-03-16T20:00:20Z

🔒 Aisle Security Analysis

We found 2 potential security issue(s) in this PR:

#	Severity	Title
1	🟠 High	Arbitrary file read/write via plugin-controlled `sessionFile` passed to `runEmbeddedPiAgent`
2	🟠 High	Privileged host agent/session helpers exposed to plugins via runtime.agent (potential privilege escalation)

1. 🟠 Arbitrary file read/write via plugin-controlled `sessionFile` passed to `runEmbeddedPiAgent`

Property	Value
Severity	High
CWE	CWE-22
Location	`src/plugins/runtime/runtime-agent.ts:16-35`

Description

runEmbeddedPiAgent is now exposed to plugins via api.runtime.agent.runEmbeddedPiAgent without any wrapper validation. A plugin can supply an arbitrary sessionFile path (absolute or ../ traversal), and the embedded runner will read and write that path on the host filesystem.

Why this is exploitable:

Entry point exposed to plugins: createRuntimeAgent() returns the raw runEmbeddedPiAgent function to plugins ([src/plugins/runtime/runtime-agent.ts 16:35]).
No path restriction on sessionFile: RunEmbeddedPiAgentParams requires sessionFile: string ([src/agents/pi-embedded-runner/run/params.ts 23:68]) and the runner passes it through unchanged.
Dangerous sinks: the attempt code uses sessionFile directly for locking/repair/open:
- Lock file creation uses the resolved sessionFile’s directory, creating directories as needed (acquireSessionWriteLock({ sessionFile: params.sessionFile, ... })) ([src/agents/pi-embedded-runner/run/attempt.ts 1715:1723]).
- Reads/writes/renames the session file and creates backups in-place (repairSessionFileIfNeeded, fs.stat, SessionManager.open(params.sessionFile)) ([src/agents/pi-embedded-runner/run/attempt.ts 1729:1752]).

Impact:

A plugin (or a user interacting with a plugin that forwards user-controlled values) can cause the agent runtime to create/overwrite files outside the intended sessions directory (e.g., sessionFile="../../.ssh/authorized_keys" or an absolute path), limited only by the OpenClaw process’s OS permissions.
This can lead to data loss, corruption of application configuration/state, or persistence (if writable sensitive files exist under the service account).

Note: there is a safer helper resolveSessionFilePath() that constrains paths to the sessions directory, but runEmbeddedPiAgent does not enforce using it, and the plugin runtime surface exposes the raw function.

Recommendation

Harden the plugin-facing API so plugins cannot select arbitrary filesystem paths.

Suggested changes:

Do not expose the raw runner directly. Export a wrapper that ignores/overrides sessionFile and resolves it internally:

// src/plugins/runtime/runtime-agent.ts
import { resolveSessionFilePath } from "../../config/sessions.js";

export function createRuntimeAgent(): PluginRuntime["agent"] {
  return {
    // ...
    runEmbeddedPiAgent: async (params) => {
      const safeSessionFile = resolveSessionFilePath(params.sessionId, undefined, {
        agentId: params.agentId,
      });
      return runEmbeddedPiAgent({
        ...params,
        sessionFile: safeSessionFile,
      });
    },
    // ...
  };
}

If you must accept a caller-provided path, enforce an allowlisted root (sessions dir) with canonicalization and rejection of absolute/.. paths (similar to resolvePathWithinSessionsDir).
Consider also restricting workspaceDir/agentDir to allowlisted roots (or per-plugin workspaces) to prevent plugins from steering agent file operations outside intended boundaries.
Add audit logging when plugins invoke agent runs (plugin id, resolved paths) and enforce reasonable limits (timeoutMs upper bound, max output, etc.).

2. 🟠 Privileged host agent/session helpers exposed to plugins via runtime.agent (potential privilege escalation)

Property	Value
Severity	High
CWE	CWE-862
Location	`src/plugins/runtime/runtime-agent.ts:16-35`

Description

createPluginRuntime() now exposes a new runtime.agent surface that passes through powerful host internals directly to plugin code (no capability checks / scoping).

Key issues:

Embedded agent execution exposed to plugins: runtime.agent.runEmbeddedPiAgent is exposed as a direct reference to the host’s embedded agent runner.
- The embedded runner accepts caller-controlled parameters such as senderIsOwner, workspaceDir, sessionFile, agentId, agentDir, etc. (see RunEmbeddedPiAgentParams), which are used by the core agent/tool policy pipeline.
- This enables a plugin to forge ownership context (e.g., pass senderIsOwner: true) and potentially unlock owner-only tool paths during an embedded run.
Session store read/write exposed to plugins: runtime.agent.session.{loadSessionStore, saveSessionStore, resolveStorePath, resolveSessionFilePath} provide direct read/write access to on-disk session metadata.
- resolveStorePath() supports {agentId} expansion, allowing a plugin to resolve and access other agents’ session stores by choosing an agentId.

Vulnerable code (newly exposed surface):

export function createRuntimeAgent(): PluginRuntime["agent"] {
  return {
    ...
    runEmbeddedPiAgent,
    ...
    session: {
      resolveStorePath,
      loadSessionStore,
      saveSessionStore,
      resolveSessionFilePath,
    },
  };
}

Why this matters:

Plugins are loaded dynamically (e.g., from workspace/global roots) and the loader explicitly warns when plugins.allow is empty, implying third-party code may be present. Exposing these helpers meaningfully expands the supported plugin capability surface and can be used for privilege escalation or sensitive data access beyond what a minimal plugin API would intend.

Recommendation

Adopt a capability-based runtime API and avoid exposing raw host internals to plugins.

Suggested mitigations:

Do not expose runEmbeddedPiAgent directly. Instead provide a constrained wrapper that:
- derives senderIsOwner, agentId, workspaceDir, sessionFile, and sandbox context from the current trusted request context (or explicitly forces safe defaults)
- refuses caller-supplied senderIsOwner, agentDir, and sessionFile
- optionally requires an explicit admin-granted capability (e.g., capabilities: ["agent:run"]) before enabling it.

Example safer wrapper shape:

export function createRuntimeAgentScoped(ctx: {
  agentId: string;
  sessionId: string;
  sessionKey?: string;
  workspaceDir: string;
  sessionFile: string;
  senderIsOwner: boolean;
}) {
  return {
    runEmbeddedPiAgent: (params: { prompt: string; model?: string; provider?: string }) =>
      runEmbeddedPiAgent({
        sessionId: ctx.sessionId,
        sessionKey: ctx.sessionKey,
        agentId: ctx.agentId,
        workspaceDir: ctx.workspaceDir,
        sessionFile: ctx.sessionFile,
        senderIsOwner: ctx.senderIsOwner,
        prompt: params.prompt,
        timeoutMs: resolveAgentTimeoutMs(/* cfg, ctx.agentId */),
        runId: `plugin-${Date.now()}`,
        // force safe defaults
        disableTools: true,
      }),
  };
}

Restrict session store access:
- Provide read-only, per-session scoped accessors (e.g., getCurrentSessionMeta()), or
- require explicit capabilities (e.g., sessions:read, sessions:write) and enforce them in the runtime factory.
- prevent arbitrary agentId selection and prevent arbitrary storePath writes.
Add runtime-level auditing/logging for any plugin invocation of privileged capabilities (agent runs, session store writes).

Analyzed PR: #48462 at commit 0f6a7ab

_{Last updated on: 2026-03-16T22:00:48Z}

* 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

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

* 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

Plugins: remove public extension-api surface

27ba829

openclaw-barnacle bot added channel: voice-call Channel integration: voice-call extensions: llm-task Extension: llm-task size: M maintainer Maintainer-authored PR labels Mar 16, 2026

greptile-apps bot reviewed Mar 16, 2026

View reviewed changes

src/plugins/loader.ts Outdated Show resolved Hide resolved

extensions/voice-call/src/response-generator.ts Outdated Show resolved Hide resolved

chatgpt-codex-connector bot reviewed Mar 16, 2026

View reviewed changes

src/plugins/loader.ts Outdated Show resolved Hide resolved

Plugins: fix loader setup routing follow-ups

c5c5ec7

Takhoffman added 2 commits March 16, 2026 15:30

CI: ignore non-extension helper dirs in extension-fast

90d7712

Docs: note extension-api removal as breaking

0f6a7ab

openclaw-barnacle bot added the scripts Repository scripts label Mar 16, 2026

Takhoffman merged commit 2de2837 into main Mar 16, 2026
31 of 38 checks passed

Takhoffman deleted the codex/remove-extension-api-public-surface branch March 16, 2026 20:51

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

📡 Upstream Digest — 2026-03-16 22:25 UTC curtismercier/openclaw-mods#283

Open

Takhoffman mentioned this pull request Mar 17, 2026

fix(tests): stabilize Windows CI cases #48544

Closed

20 tasks

alfredomenezes mentioned this pull request Mar 20, 2026

Gateway hangs on startup after plugin system refactor (never binds port) #50744

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Plugins: remove public extension-api surface#48462

Plugins: remove public extension-api surface#48462
Takhoffman merged 4 commits intomainfrom
codex/remove-extension-api-public-surface

Takhoffman commented Mar 16, 2026

Uh oh!

greptile-apps bot commented Mar 16, 2026

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

Uh oh!

aisle-research-bot bot commented Mar 16, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

Takhoffman commented Mar 16, 2026

Summary

Verification

Uh oh!

greptile-apps bot commented Mar 16, 2026

Greptile Summary

Confidence Score: 3/5

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

aisle-research-bot bot commented Mar 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔒 Aisle Security Analysis

1. 🟠 Arbitrary file read/write via plugin-controlled sessionFile passed to runEmbeddedPiAgent

Description

Recommendation

2. 🟠 Privileged host agent/session helpers exposed to plugins via runtime.agent (potential privilege escalation)

Description

Recommendation

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

aisle-research-bot bot commented Mar 16, 2026 •

edited

Loading

1. 🟠 Arbitrary file read/write via plugin-controlled `sessionFile` passed to `runEmbeddedPiAgent`