DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to make an encrypted backup of your WeChat history with Greenbubbles

Create a copy of your chat history protected by a 24-word recovery phrase, readable later without WeChat.

Credentials. Losing the 24-word recovery phrase means the encrypted backup cannot be opened, and pasting it into an agent prompt exposes it.

Who it is forA person who wants a durable copy of years of chat history before changing phones or after a WeChat update.

The problemYour history lives inside WeChat's own files, which you cannot easily keep, move, or open without the app.

The outcomeAn encrypted snapshot of your history that you can open later, as long as you keep the 24-word recovery phrase.

What you need first

  • A Mac with Apple silicon running macOS 14 or later
  • WeChat installed and running on that Mac
  • Administrator access for the one-time key setup
  • Homebrew, or the DMG or ZIP from the Releases page
  • A coding agent such as Claude Code, Codex, or Gemini CLI, if you want agent-written notes

Steps

  1. Run brew tap bojieli/greenbubbles https://github.com/bojieli/greenbubbles.git
  2. Run brew install bojieli/greenbubbles/greenbubbles
  3. Read docs/RECOVERABLE_SNAPSHOTS.md for the snapshot steps
  4. Create the snapshot following that guide, and write down the 24-word recovery phrase
  5. Store the recovery phrase and the backup in separate safe places

Prompt for your agent

Following docs/RECOVERABLE_SNAPSHOTS.md in the repo bojieli/greenbubbles, help me create an encrypted snapshot of my WeChat history. Report the snapshot location and confirm the 24-word recovery phrase was shown. Verify that the recovery phrase is not written to any file or sent in a prompt.

Caveat. The backup contains private messages, so the README says to protect it as carefully as WeChat's own data.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page