PR #55622: fix(channels): use pinned channel registry in createChannelRegistryLoader

• Repository: openclaw/openclaw
• Author: jsonmez
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/55622

Description (problem / solution / changelog)

Problem

createChannelRegistryLoader (used by loadChannelOutboundAdapter) calls getActivePluginRegistry() which is the unpinned active registry. When anything triggers a transient setActivePluginRegistry() call — config-schema reads, maybeBootstrapChannelPlugin, loadOpenClawPlugins for non-primary contexts — the activeRegistry pointer changes.

When registry !== lastRegistry, the loader cache is cleared. The new (possibly empty or different) registry no longer contains the channel plugin, causing:

Outbound not configured for channel: telegram
Outbound not configured for channel: slack

Subagent completions silently fail to announce back. Retries all fail because the registry state persists.

Fix

Use requireActivePluginChannelRegistry() — the pinned startup registry — matching what getChannelPlugin() already does. Two-line change.

Testing

Verified locally on macOS (arm64), OpenClaw v2026.3.24, Telegram channel. Before fix: subagent announce failed consistently. After fix: announce delivers reliably.

Related Issues

• Closes #55551
• Related: #55382 (same root cause, Slack — includes deeper analysis)
• Related: #14188 (original Telegram report, v2026.2.9)

Changed files

• src/channels/plugins/registry-loader.ts (modified, +2/-2)

PR #55988: fix(outbound): fall back to pinned channel-surface registry in registry loader

• Repository: openclaw/openclaw
• Author: TurboTheTurtle
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/55988

Description (problem / solution / changelog)

Problem

Isolated cron job delivery and subagent announce-back intermittently fail with:

• Outbound not configured for channel: discord
• Unsupported channel: discord

This happens when a non-primary plugin reload (config-schema read, provider snapshot, etc.) replaces the active plugin registry with a minimal set that omits channel plugins. The outbound registry loader (createChannelRegistryLoader) only checks the active registry, missing the channel that was fully loaded at gateway startup.

Root Cause

The channel-surface registry is pinned at gateway startup via pinActivePluginChannelRegistry() and is immune to subsequent registry swaps. However, createChannelRegistryLoader (used by loadChannelOutboundAdapter) only reads from getActivePluginRegistry() — not the pinned channel surface.

This means getChannelPlugin("discord") (which uses requireActivePluginChannelRegistry()) succeeds, but loadChannelOutboundAdapter("discord") fails — they see different registries.

Two prior fixes attempted to address this:

• fa6ff39 — added resolveDirectFromActiveRegistry fallback
• 0c2ae71 — added resolveOutboundChannelPlugin call before loadChannelOutboundAdapter

Both fixes resolve the plugin from the active registry — which is exactly the registry that gets swapped out. Neither falls back to the pinned channel surface.

Fix

Add a fallback in createChannelRegistryLoader to check the channel-surface registry when the active registry does not contain the requested channel. This mirrors what getChannelPlugin already does via requireActivePluginChannelRegistry.

The fallback only activates when the channel-surface registry is a different (pinned) object from the active registry, avoiding unnecessary lookups in the common case.

Testing

• 5 new unit tests covering: normal resolution, missing channel, pinned fallback, same-registry no-fallback, and cache invalidation
• All existing runtime.channel-pin, channel-resolution, and outbound tests pass

Fixes #12769 Refs #14266, #55551, #54745

Changed files

• src/channels/plugins/registry-loader.test.ts (added, +109/-0)
• src/channels/plugins/registry-loader.ts (modified, +32/-4)