# WhatsApp CLI

> **TL;DR.** WhatsApp CLI refers to a new wave of command-line clients that speak the WhatsApp Web multidevice protocol so terminals, shell scripts, and AI agents can read, search, and send messages.

- **Category:** Developer Tools / Messaging / Automation
- **Stage:** rising
- **Age:** 173 days
- **Origin date:** 2025-12-12
- **First detected:** 2026-04-18
- **Canonical URL:** https://earlyterms.com/term/whatsapp-cli
- **Sources:** 6 primary URLs

## Definition

WhatsApp CLI refers to a new wave of command-line clients that speak the WhatsApp Web multidevice protocol so terminals, shell scripts, and AI agents can read, search, and send messages. They authenticate via QR-code scan, sync message history locally (SQLite FTS5 or equivalent), and emit structured JSON — making WhatsApp pipeable into a Claude Code or Codex agent loop.

The category catalyzed around Peter Steinberger's [wacli](https://github.com/steipete/wacli), released December 12, 2025, which reached 1,950 stars and hit the [Hacker News front page at 246 points on April 15, 2026](https://news.ycombinator.com/item?id=47775628). Parallel efforts include Vicente Reig's [whatsapp-cli](https://github.com/vicentereig/whatsapp-cli) ('Give your codex/claude access to WhatsApp') and Wassist's [cli](https://github.com/Wassist/cli) ('WhatsApp CLI without getting banned').

## Example

With `wacli` installed via Homebrew, a developer can pipe `wacli send --phone +15551234 --text "deploy complete"` into CI, or feed 12 months of history into an agent for summarization. All flows ride the unofficial `whatsmeow` Go library; Meta doesn't sanction it, and ban risk is real for high-rate senders.

## Analogy

WhatsApp CLI is to WhatsApp what sendmail was to email — an unofficial pipe into a walled garden, invaluable for scripting, easy to get your account killed with.

## Why it's emerging now

Steipete's wacli hit 246 points on HN and 1,950 stars in four months. At the same time AI agents (Claude Code, Codex) created a new use case: give a coding agent chat access so it can ping the team when CI finishes. Vicente Reig's project README says the quiet part aloud: 'Give your codex/claude access to WhatsApp.'

## Related terms

- *alias:* wacli
- *related:* whatsmeow
- *related:* nchat
- *related:* yowsup
- *related:* claude-code
- *related:* openai-codex-cli
- *related:* agent-harness
- *competitor:* WhatsApp Business API
- *competitor:* Telegram Bot API
- *related:* Matrix protocol

## Sources

1. [steipete/wacli (1,950 stars)](https://github.com/steipete/wacli)
2. [Hacker News — Wacli discussion (246 points)](https://news.ycombinator.com/item?id=47775628)
3. [vicentereig/whatsapp-cli](https://github.com/vicentereig/whatsapp-cli)
4. [Hacker News — WhatsApp CLI without getting banned](https://news.ycombinator.com/item?id=47804372)
5. [whatsmeow — underlying Go library](https://github.com/tulir/whatsmeow)
6. [eddmann.com — WhatsApp CLI overview](https://eddmann.com/whatsapp-cli/)

---
_Generated by EarlyTerms · https://earlyterms.com/term/whatsapp-cli_