WeChatBridge starts with the messages you explicitly export
Select a useful conversation in WeChat, forward it to WeChatBridge, and send the resulting archive to an agent or your notes folder. That is the project's appeal: it connects a deliberate export to the application where you want to work on it. WeChatBridge's main README is Chinese, with a separate English README and bilingual interface. It handles the transfer and local organization. Any interpretation of the conversation belongs to the receiving agent.
The English README identifies WeChat 4.1.13 for macOS as the starting point for merged forwarding to other apps. WeChat produces a ZIP containing text and media, while WeChatBridge supplies the missing share-menu destinations. This is a useful boundary for someone who wants selected chat material in a knowledge base without granting a tool access to the full messaging database. It also means selecting the source conversation remains part of your workflow.
What happened when we ran it
We did not run WeChatBridge: our harness did not support its Swift ecosystem, and the repository had no Dockerfile. The lab recorded that limitation for commit 0b00e3f on October 8, 2026. Its unprivileged environment had no secrets. There is no installation timing, build result, test count, or dependency audit from this attempt. Treat the review as an assessment of the documented workflow and current repository evidence, with runtime behavior still unverified by us.
That boundary matters most around desktop integration. Receiving an exported ZIP, registering a share extension, finding the destination window, and pasting into the intended input are different operations. A description of those operations cannot tell you whether your Mac permissions and application versions cooperate. Before relying on the archive, check a short conversation with recognizable attachments and confirm both the saved material and the destination application yourself.
macOS 14 is the documented route, with Intel support included
The macOS requirements name Sonoma or later, with Xcode 16 or Swift 6-compatible command-line tools for source work. The downloadable DMG supports both Intel and Apple Silicon. Accessibility permission enables automatic paste, while Screen Recording supports recognition of the chat name from the title bar. If you prefer fewer permissions, the clipboard destination leaves the final paste to you. The usage guide also explains where macOS exposes the extension switches.
Release v0.1.15 is described as Developer ID signed and Apple notarized. An open signature-check report, however, says the reporter could not validate that official DMG. The report also records local signing-subsystem errors and explicitly leaves the cause unresolved. It is a reason to verify the downloaded app on your own Mac, not evidence that the release is universally broken. Local development signing can also require renewed Accessibility permission.
Local archiving stops being local when another app receives it
The English README says the share extensions run in a macOS sandbox without network access. Archives, prompts, and records stay on the Mac, and the app does not decrypt or inject into WeChat. Those are specific design claims worth checking. Once an archive reaches a cloud-connected agent, that agent's data handling applies. Choosing the Obsidian or folder destination has a different exposure from handing the same conversation to a hosted model.
Automatic update checks are currently disabled in the documented source configuration. Screen capture is described as title recognition, with images processed in memory. The older capabilities document adds another useful distinction: the host app itself is outside App Sandbox because it manages extensions, even though the extensions are sandboxed. Read that boundary carefully if your deployment policy requires every installed component to remain sandboxed.
Obsidian keeps the original ZIP beside the readable note
The archive path creates Markdown from the exported text while preserving the original package and organizing notes by chat name. That gives you something readable and a source artifact to return to when an agent summary misses a detail. Scene prompts can travel with an export, so a project conversation can carry the same extraction instructions each time. Custom destinations can receive file paths, which is useful for terminal-oriented tools.
The current README also describes collecting exports in batches, but the capabilities document labels that path as implemented in development with the WeChat-host sharing flow awaiting real-device verification. Release v0.1.15 predates some of the current menu descriptions. Check whether a feature exists in the downloaded package before designing a recurring workflow around it. The repository's current source, its older capability inventory, and its stable release describe different stages of the project.
October activity includes a Windows naming defect
GitHub listed 1,334 stars, a last push of October 10, 2026, and 10 open issues and PRs. Current source includes a Windows solution. An open Windows report describes exports from different groups merging into one note because their detected name becomes the same generic WeChat title. The report concerns the Windows test version. It cannot establish that the macOS archiver has the same defect.
Dukou, the acknowledged upstream project, is worth considering when text backups and offline HTML previews matter more than scene-driven archiving. Chatbox suits someone happy to submit selected material manually in a separate AI client. WeChatBridge is the more specific choice for a repeated WeChat-to-Obsidian or agent transfer. Start by checking the destination note name and original ZIP. A successful paste is only useful if the archive still belongs to the right conversation.