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

How to find a past message in one WeChat chat by keyword with Greenbubbles

Search the text of a single conversation from the command line without scrolling through WeChat.

Credentials. Setup needs the one-time key copy from your WeChat app, which requires administrator access.

Who it is forA person who remembers a detail from an old chat, such as an address, a date, or a promise, and wants it fast.

The problemWeChat's own search is slow to scan old history, and scrolling through a long chat is tedious.

The outcomeA JSON Lines list of matching messages from that chat, with sender, local time, and text, plus a cursor if more results exist.

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. Run greenbubbles chats find "Alice" to confirm the chat name
  4. Run greenbubbles messages search --conversation "Alice" --query "keyword"
  5. If the output says hasMore: true, run the same command with --cursor set to the nextCursor value

Prompt for your agent

Use the greenbubbles CLI from the repo bojieli/greenbubbles to search one chat. Run `greenbubbles messages search --conversation "<chat name>" --query "<keyword>"` and report the matching messages as JSON Lines. Verify that every returned message has its chat name and local time before you summarize it.

Caveat. Setup requires the key capture from your running WeChat app, and the README says WeChat may change its private formats, so an update can break reading.

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