wacli

Why it's ranked here

The tool has unusual depth for terminal automation. Structured output, lifecycle events, read-only safeguards, storage caps, webhooks, and delegated sends make it suitable for serious scripts, not just interactive commands. Its value depends on accepting an unofficial protocol and incomplete historical coverage, so it is capable but operationally fragile.

What's good

Automation boundaries are thoughtful. Normal results go to standard output while progress and errors stay separate. One-shot commands emit JSON, long-running work emits newline-delimited events, and read-only mode blocks mutations. Store locks prevent competing sessions, while a continuous sync process can safely handle supported sends from other commands.

Tradeoffs

WhatsApp Web supplies history only on a best-effort basis, so this cannot promise a complete archive. The protocol is unpublished and upstream changes may break compatibility. Sending confirms WhatsApp accepted a request, not recipient delivery. Webhooks do not retry, media transfers are capped, and some interactive message controls remain unsupported.

How to use it well

Use it for shell pipelines, coding agents, searchable personal archives, bounded message capture, and carefully paced outbound automation. Keep continuous sync running, set storage limits, choose quiet presence when appropriate, and give analysis tools read-only access. It does not replace a GUI, an MCP server, guaranteed archival software, contact creation, or voice calling.

Observed

License

MIT

Primary language

Go

Interface

Command-line application with human-readable, JSON, and NDJSON output modes

Platforms

macOS, Linux, and Windows

Installation

Homebrew, prebuilt release archives, Docker guidance, and Go source installation

Packaging

Single binary built with cgo and SQLite FTS5 support

Storage

Separate SQLite databases hold the WhatsApp session and the local message index

Integration surface

Signed webhooks can emit message, receipt, and chat-presence events