Wacli
- 2.3k installs
- 385k repo stars
- Updated August 3, 2026
- steipete/clawdis
wacli is a skill for third-party WhatsApp messaging and history search via the wacli CLI, not routine user chats.
About
The wacli skill documents the wacli CLI for third-party WhatsApp messaging and history sync, explicitly not for normal active user chats routed by OpenClaw. Safety rules require explicit recipient and message text with confirmation before send. Auth uses wacli auth QR login, wacli sync --follow for continuous sync, and wacli doctor for health checks. Chat discovery and message search support query filters, chat JIDs, and date ranges. History backfill requests additional messages when the phone stays online. Send covers text, group JIDs ending in @g.us, and file messages with captions. Storage defaults to ~/.wacli with optional --store override and --json for parsing. Install paths include Homebrew steipete/tap/wacli or go install from github.com/steipete/wacli. Agents should only reach for wacli when the user asks to message someone else on WhatsApp or to search synced history, never for routine conversation on the same WhatsApp thread.
- Third-party WhatsApp send and history sync only; not normal user chats.
- Requires explicit recipient, message text, and confirmation before send.
- Auth via QR, continuous sync, chat search, and history backfill.
- Send text, group messages, or files with captions via CLI flags.
- Install with brew steipete/tap/wacli or go install module path.
Wacli by the numbers
- 2,324 all-time installs (skills.sh)
- +2 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #172 of 2,719 Automation & Workflows skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 3, 2026 (Skillselion catalog sync)
wacli capabilities & compatibility
- Capabilities
- qr auth and continuous whatsapp sync · chat list and message search with filters · text, group, and file send with safety confirmat · history backfill for additional messages · explicit exclusion of routine user chat routing
- Use cases
- orchestration · email
npx skills add https://github.com/steipete/clawdis --skill wacliAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.3k |
|---|---|
| repo stars | ★ 385k |
| Security audit | 2 / 3 scanners passed |
| Last updated | August 3, 2026 |
| Repository | steipete/clawdis ↗ |
How does an agent send WhatsApp messages to someone else or search synced chat history safely?
Send WhatsApp messages to third parties or sync and search WhatsApp history via wacli when explicitly requested, not for normal user chats.
Who is it for?
Explicit third-party WhatsApp outreach or historical message search via wacli.
Skip if: Skip for normal OpenClaw WhatsApp user conversations or unsolicited messaging.
When should I use this skill?
User asks to WhatsApp a third party, sync history, search messages, or install wacli.
What you get
Authenticated wacli session with confirmed send or structured search results from local store.
- Sent WhatsApp messages
- Synced local message store
- JSON CLI command output
By the numbers
- Documents 2 install paths: Homebrew steipete/tap/wacli and Go module install
- Underlying wacli CLI stores messages in SQLite with FTS5 search index
Files
wacli
Use wacli only when the user explicitly asks you to message someone else on WhatsApp or when they ask to sync/search WhatsApp history. Do NOT use wacli for normal user chats; OpenClaw routes WhatsApp conversations automatically. If the user is chatting with you on WhatsApp, you should not reach for this tool unless they ask you to contact a third party.
Safety
- Require explicit recipient + message text.
- Confirm recipient + message before sending.
- If anything is ambiguous, ask a clarifying question.
Auth + sync
wacli auth(QR login + initial sync)wacli sync --follow(continuous sync)wacli doctor
Find chats + messages
wacli chats list --limit 20 --query "name or number"wacli messages search "query" --limit 20 --chat <jid>wacli messages search "invoice" --after 2025-01-01 --before 2025-12-31
History backfill
wacli history backfill --chat <jid> --requests 2 --count 50
Send
- Text:
wacli send text --to "+14155551212" --message "Hello! Are you free at 3pm?" - Group:
wacli send text --to "1234567890-123456789@g.us" --message "Running 5 min late." - File:
wacli send file --to "+14155551212" --file /path/agenda.pdf --caption "Agenda"
Notes
- Store dir:
~/.wacli(override with--store). - Use
--jsonfor machine-readable output when parsing. - Backfill requires your phone online; results are best-effort.
- WhatsApp CLI is not needed for routine user chats; it's for messaging other people.
- JIDs: direct chats look like
<number>@s.whatsapp.net; groups look like<id>@g.us(usewacli chats listto find).
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.591k39.6k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.494kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.493kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.492kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.492k
Twitter AutomationAutomate X/Twitter posts, scheduling, and engagement via X API integration441k669Forks & variants (1)
Wacli has 1 known copy in the catalog totaling 1 installs. They canonicalize to this original listing.
- letta-ai - 1 installs
How it compares
Pick wacli over generic shell scripting when WhatsApp-specific QR pairing, offline FTS search, and deterministic --json CLI output are required.
FAQ
When should I not use wacli?
Do not use for normal user chats; OpenClaw routes those automatically unless contacting a third party.
What safety checks are required before send?
Require explicit recipient and message text, confirm both, and ask if anything is ambiguous.
Where are messages stored?
Default store is ~/.wacli, overridable with --store; use --json for machine-readable output.