OpenClaw has removed five deprecated plugin SDK entrypoints, a breaking change that plugin developers will need to address before upgrading the host. The change also removes 869 export paths while adding 35 focused alternatives, with no signature changes to exports that remain.
OpenClaw Watch analysis
What happened
A 1 October commit in the OpenClaw repository retires the compatibility facades for channel lifecycle, channel messages, reply pipelines, configuration runtime and infrastructure runtime. The commit directs developers to focused channel, configuration and infrastructure entrypoints instead; a new system-event-runtime entrypoint provides public snapshot inspection and consumption.
The project’s commit says in-repository callers have been migrated and that package exports, SDK inventories, compatibility tombstones and migration documentation were updated. It specifically warns developers to update affected external plugins before upgrading the host, and does not claim that every external plugin has migrated.
Why it matters
Plugin authors have a concrete compatibility check to make: code importing any of the five retired paths must move to the replacement entrypoints before the host upgrade. The 869 removed paths make this more than a tidy rename, even though the commit reports no signature changes among the exports that remain.
Our read
This is a clear break with a useful migration signal, not a reason to assume every plugin will sail through. Check imports against the retired list and test affected plugins against the new entrypoints before upgrading. Compatibility is lovely; knowing exactly where it ends is more useful.
What to watch
- Whether the migration documentation gives external plugin authors practical examples for each replacement.
- Whether plugin maintainers report breakage beyond the five named entrypoints.
- Whether later OpenClaw releases add further compatibility removals or migration support.
Discussion spark: Should plugin projects favour a cleaner API even when it means breaking older integrations, or keep compatibility layers for longer?
Sources and evidence
- refactor(plugin-sdk)!: retire deprecated compatibility facades (162333) (1 October 2026, 11:12 UTC)
OpenClaw Watch is independently operated by WittyWires. It is not affiliated with, endorsed by, or operated by the OpenClaw Foundation.