Wacli – WhatsApp CLI

Original Article ↗ Hacker News Discussion ↗

Project reception & perceived value

  • Many see a WhatsApp CLI as a badly needed integration point, especially as WhatsApp is becoming a de‑facto control plane for AI and internal tooling.
  • Offline search with FTS5 over full chat history is praised; in‑app WhatsApp search is described as slow and painful.
  • Some question who will actually use a CLI, but others note devs are end‑users too, and CLIs provide speed, automation, and composability.

Implementation details: whatsmeow vs Baileys

  • whatsmeow is described as more stable and actively maintained than Baileys, used in production bridges.
  • Neither library requires a browser; they can run in mobile apps.
  • There’s curiosity about how many numbers get “burned” during development and whether this will trigger bans.

Risk of bans & Terms of Service

  • Multiple commenters report bans or suspensions for using third‑party clients, sometimes even when only logging in.
  • Advice: never use this with an account you care about; consider separate / throwaway numbers.
  • Some report bans reversed on appeal; others say bans were permanent for secondary accounts.
  • Even with Meta’s official APIs, automation is heavily restricted (24‑hour reply window, mandatory templates, verification, business focus).

Security, encryption & metadata

  • Debate over how “real” WhatsApp’s end‑to‑end encryption is:
    • One side: uses Signal Protocol; Meta staff cannot read messages.
    • Other side: closed-source app, forced updates, and potential backdoors mean practical insecurity.
    • Clarifications that cloud backups (iCloud/Google) are outside WhatsApp’s E2EE.
  • Confusion and disagreement around multi‑device E2EE behavior and whether messages route through a primary device.

Alternatives: Telegram, Matrix, SMS, others

  • Telegram is praised for its bot API and automation‑friendliness, but criticized for lack of default E2EE, potential compromise claims (which other commenters challenge and demand proof for), and metadata visibility.
  • Matrix is highlighted as a fully E2EE, self‑hostable, automation‑friendly alternative with simple bot users and no API bean‑counting; several people move to Matrix due to friction with WhatsApp and Slack.
  • SMS is seen as insecure and clunky but sometimes more robust for identity; virtual/VoIP numbers are discussed as throwaway options with caveats.

AI agents, CLIs, and platform control

  • Many see tools like this as primarily for AI agents to interact with WhatsApp, not just humans at a terminal.
  • There’s concern Meta may clamp down further as AI use grows, already disallowing general‑purpose chatbots via official channels.
  • Some argue WhatsApp’s tight control and limited APIs are what keep it relatively spam‑free; open protocols are seen as more spam‑prone.