Two generations of WeChat chat-history exporters have ~55k combined…
Two generations of WeChat chat-history exporters have ~55k combined stars and issue trackers full of people offering to pay — yet every one of them stops at 'export + a one-off yearly report'; nobody has built the archive you can keep asking questions of.
What is the idea?
WeFlow and WeChatMsg decrypt a user's own local WeChat database and dump it to readable form; robbin/wechat-exporter (2026-07-28) compresses the whole chain — re-sign the client, pull the DB key from memory, decrypt to plaintext SQLite, register it as an MCP server — into a single Claude Code / Codex skill.
Who would use it, and what do they get?
An adult child with ten years of family group chat and a parent's voice notes sitting encrypted on their own laptop. What they get is one conversation printed as a keepsake book, and the ability to ask that conversation a question — with nothing ever leaving the machine. The export is plumbing; the book is the product.
Why would anyone bother?
For a huge number of people WeChat is the single densest record of their life: a decade of family group chats, a parent's voice notes, a relationship from first message onward. It is local, encrypted, unsearchable across years, and routinely destroyed on device change.
What is missing today?
Everything that exists is either a CLI/skill only a developer can run, or a one-shot 'year in review' poster — nobody has built the durable, ask-anything archive on top of the corpus.
What makes this one different?
Don't compete on exporting — start after the export, with one narrow job: pick a single family conversation, answer questions about it locally, and print it as a keepsake book. Cold start (Chinese): message the people in the WeFlow and WeChatMsg issue trackers and fork lists who are asking for a Mac build or an unexpired binary, then the comment sections of Xiaohongshu posts searched for 微信聊天记录 导出. Cold start (English): r/DataHoarder and r/China_irl, search 'WeChat export'. 补(2026-08-07)：keepsake book 这一半不再是假设，需求侧已被两种独立行为证明。中文侧——《45w人看过的聊天记录图册教程》3,692赞/3,013收藏，教的是把聊天记录逐条截图、导进 InDesign 手工排版再送印刷店；同族还有《三年聊天记录，做成了3700多页的电子书》367赞、《打印微信聊天记录长图步骤》226赞。教程排在产品前面、且教的是纯手工流程——与 #577 体检报告那条同一形状。英文侧——一位美国用户把家庭群聊印成传家宝的视频转到小红书拿到 855 赞，评论来自美英两地。结论：改动优先级——先做「导出后 → 一本可印的书」这一段，而不是先做 ask-anything 归档；书是今天就有人在手工做、并愿意跑印刷店的那个成品。
What is the sharpest thing about it?
The export step, which used to be a fragile multi-hour ritual, is now one command that ends with the corpus already wired into an agent you can talk to.
What could kill it?
WeChatMsg has been at this since 2023 with 41.9k stars, so a well-funded incumbent could appear; decryption breaks whenever the desktop client updates (WeFlow's own users are currently stuck on an expired build), and the platform has no incentive to make this stable.
Who pays, and for what?
One-time paid desktop app, plus printed keepsake books as the upsell — the same buyers who already pay shops to digitise family media.
What is the main risk?
Decryption is version-fragile and sits in a grey zone with the platform's terms even though it is the user's own data; the product must be strictly local, own-data-only, with no cloud copy.
What did real people actually say?
Verbatim from the public sources linked above, not paraphrased: “xdm，来份源码发我邮箱行吗，有偿也行的” — github-issue “我的聊天记录不是我自己的” — github-issue “我的隐私不是我的” — github-issue “6.1.0版本的exe怎么expire了。希望大佬速速更新。” — github-issue “速搓傻瓜版教程，按图片一步步做就可以啦。需要的材料：电脑、截好图的聊天记录” — xiaohongshu “宝你这个就是满版没拉到出血线，背景大小要跟纸页外面那个红色的框框一样大，而且图片都没嵌入还是链接你快改一下” — xiaohongshu “Printed my family's group chat so I can pass it down as an heirloom.” — xiaohongshu-repost
How much work is it?
about two months of work
Where does the evidence come from?
https://github.com/hicccc77/WeFlow https://github.com/hicccc77/WeFlow/issues https://github.com/LC044/WeChatMsg https://github.com/robbin/wechat-exporter
← Both language sides asked for the same missing thing this year · Turning your handwriting into a real font went to one photo and… →