跪拜 Guibai
← All articles
Backend

Open-Source WeChatBridge Hits iOS: Pipe WeChat Chats to AI Agents and Obsidian Straight From Your Phone

By 苍何 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

WeChat's chat records rarely leave the phone; this app changes that with a share-sheet flow that pipes them to AI agents and Obsidian without touching a desktop. The development method is the other half: acceptance-spec-driven agent work compressed 18 working days into six hours and is directly transplantable to any long-horizon coding task.

Summary

WeChatBridge, the open-source tool that forwards WeChat chat logs to AI agents and Obsidian, now runs on iOS. The new app works from the system share sheet: pick messages in WeChat, forward them to WeChatBridge, and they land as cards in an on-device inbox. From there you can send them to ChatGPT, Doubao, Qwen, Claude, DeepSeek, or Obsidian, with scene-specific prompts that auto-copy. Over 100 messages are handled by batch collection with dedup. Everything stays on device; no server upload. The app is in App Store review, with early access through the GitHub community.

The development story is just as notable. The team gave Kimi K3.1 Pro, a Chinese open-source model, a detailed spec and acceptance criteria, then let it run the whole 18-working-day plan in about six hours. The key was not describing requirements but defining "done": each milestone had exit gates with explicit simulator and real-device tests, and the agent self-checked its own output, finding and fixing five bugs during acceptance runs. The lesson the author draws: "Don't chat about requirements with it; define acceptance with it."

Takeaways
— WeChatBridge has 1,700+ GitHub stars and now supports Mac, Windows, and iOS.
— The iOS version is in App Store review; early access is via the project's GitHub community.
— Users forward WeChat messages via the share sheet; the app stores them as cards in an on-device inbox.
— Each card can be sent to ChatGPT, Doubao, Qwen, Claude, DeepSeek, or Obsidian, with scene-specific prompts auto-copied.
— For apps that reject ZIP files, WeChatBridge converts chat exports to a PDF with inline images.
— WeChat caps a single forward at 100 messages; WeChatBridge supports batch collection that merges multiple batches and dedupes overlapping messages.
— Obsidian delivery writes a structured Markdown note with sender, time, inline images, and attached original ZIP.
— All processing stays on-device; no server upload, and it uses only WeChat's official share and Apple's share sheet.
— Kimi K3.1 Pro, a Chinese open-source model, generated the iOS v1 in about 6 hours, versus the 18 working days the plan estimated.
— The agent self-checked against acceptance rules and fixed five bugs it found during simulator verification.
Conclusions

The acceptance-spec method is the real differentiator: the model ran 18 days of planned work in six hours because every milestone had exit gates, and unverifiable items were explicitly marked "pending real device" instead of being waved through. That discipline, not the model's raw power, is what made the agent self-correcting.

Kimi K3.1 Pro's performance on a multi-hour autonomous coding run, including finding and fixing its own bugs, suggests open-source Chinese models are now competitive with frontier models for long-context engineering tasks, not just code generation.

Concepts & terms
Exit gate
A milestone checkpoint in the development spec that lists explicit verification steps; work cannot proceed to the next milestone until all checks pass.
Share sheet relay
An iOS pattern where a share extension receives forwarded files (like exported chat ZIPs) and passes them to the main app for storage and delivery, without leaving the original conversation.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗