Cherry-pick 0ce23dc62d: move iMessage channel to extensions/imessage#2038
Merged
alexey-pelykh merged 1 commit intomainfrom Mar 29, 2026
Merged
Conversation
…openclaw#45539) Move iMessage adapter implementation from src/imessage/ to extensions/imessage/src/, replacing src/ files with re-export shims. Resolves rebrand conflicts (OpenClawConfig → RemoteClawConfig) and adds self-chat-cache module from upstream. Cherry-picked-from: openclaw/openclaw@0ce23dc62d Co-authored-by: scoootscooob <[email protected]>
This was referenced Mar 29, 2026
alexey-pelykh
deleted the
cherry-pick/0ce23dc62d-imessage-extensions-move
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick from upstream
Upstream commit:
0ce23dc62dAuthor: scoootscooob
Tier: AUTO-PICK
Issue: #2027
Moves iMessage adapter implementation from
src/imessage/toextensions/imessage/src/, replacing the original files with re-export shims. This mirrors the upstream extensions-move pattern already applied for WhatsApp (#2032, #2035).Conflict Resolution
7 conflicts resolved:
src/imessage/re-export stubs (accounts.ts,monitor/types.ts,monitor/inbound-processing.ts,monitor/monitor-provider.ts,monitor/self-chat-cache.ts): Fork had rebranded full implementations; replaced with upstream re-export shims pointing to new extension pathsextensions/imessage/src/monitor/inbound-processing.test.ts: Rebrand conflict in import path — accepted upstream pathsextensions/imessage/src/monitor/self-chat-cache.test.ts: Rename/delete — file didn't exist in fork (from unpicked12dc299cd); accepted upstream versionextensions/imessage/src/monitor.gating.test.ts: Nested conflict markers from rename collision; accepted upstream versionRebrand Applied
OpenClawConfig→RemoteClawConfigacross all new extension files[email protected]→[email protected]in SSH example comment@openclaw→@remoteclawin mention pattern test fixturesPost-pick verification
pi-agent-core,pi-ai,pi-coding-agent).ai,.com)openclawreferences in changed filestsgotypecheck passes (exit 0)oxfmt --check)Note on follow-up commits
The issue originally specified partial picks of
c1ef5748ebanda622eecd3b, but investigation shows:c1ef5748ebtouches 3 iMessage files (setup-core.ts,setup-surface.ts,shared.ts) that don't exist in the fork — they're created by blocked plugin system cherry-picks (Cherry-pick (blocked): Plugin system (1/2) (50 commits) #1940/Cherry-pick (blocked): Plugin system (2/2) (33 commits) #1941)a622eecd3bhas zero iMessage filesBoth follow-up commits are no-ops in the current fork state.
Files changed
55 files: 32 new in
extensions/imessage/src/, 20 modified insrc/imessage/(now re-export shims), 3 deleted (tests moved to extensions)