feat: JSON-RPC daemon with full messaging support + LID routing#83
Open
g1e2x87 wants to merge 10 commits intosteipete:mainfrom
Open
feat: JSON-RPC daemon with full messaging support + LID routing#83g1e2x87 wants to merge 10 commits intosteipete:mainfrom
g1e2x87 wants to merge 10 commits intosteipete:mainfrom
Conversation
added 7 commits
February 22, 2026 07:06
WhatsApp now uses Linked IDs (@lid) instead of traditional JIDs (@s.whatsapp.net). This causes reply routing failures when the daemon receives events with LID-format chatJid/senderJid. Changes: - daemon.go: add resolvedJid field to event payload, resolve @lid to @s.whatsapp.net for DM chats - methods.go: resolve @lid recipients before sending in rpc_send - client.go: add ResolveRecipientJID(), IsLIDJID(), GetUserInfo() using whatsmeow store.GetAltJID + GetUserInfo fallback - app.go: extend WAClient interface with new methods - fake_wa_test.go: sync fake implementation
added 3 commits
February 27, 2026 03:37
- daemon.go: fallback to WA server GetGroupInfo when cache/DB miss for group name - daemon.go: add --lock-wait flag with 45s default for SQLite lock contention - rpc/server.go: improve connection handling and cleanup - rpc/events.go: enhance event delivery reliability - rpc/methods.go: robustness improvements for RPC methods
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.
Summary
Complete JSON-RPC 2.0 daemon implementation for wacli, enabling external applications (AI agents, bots) to interact with WhatsApp programmatically via TCP or stdio.
Commits
b05cd13): Core JSON-RPC daemon —send,subscribe,listChats,getMessages0c03b27):sendReaction,remoteDelete,sendFile,searchMessages, enhanced eventse125b51):groupNamein events,getGroupInfo/getContactNameRPC methods1e0732b):GetChatfallback for group name lookupb829f05):selfJidin message events for self-identification8a7747c): Pre-populate group names + in-memory cache for event handler9dd9687): Resolve WhatsApp Linked IDs to traditional JIDs for reply routingFeatures
--transport tcp --listen addr) or stdio (default)send,sendFile,sendReaction,remoteDelete,listChats,getMessages,searchMessages,getGroupInfo,getContactName,subscribesubscribepushes real-timemessage.received,message.sent,typing,presencenotifications@lidJIDs to@s.whatsapp.netfor reliable message deliveryTesting
go build ./cmd/wacli/passes