메뉴
Send WhatsApp messages, list chats, and search history via wacli (local CLI backed by a synced store at ~/.wacli). Unpaired? Run the guided connect flow (scripts/guided_connect.py) from chat — no terminal needed.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/sonichi/sutando --skill whatsapp명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Infer stable semantic workstreams for ungrouped Sutando task history and apply the validated assignments to the durable workstream sidecar. Use for internal task-workstream-grouping maintenance tasks, initial history backfills, and later batches of tasks that need cross-channel or cross-device workstream organization.
Start Sutando's autonomous proactive loop. Monitors tasks, runs health checks, and builds missing capabilities on a recurring schedule.
Make conversational phone calls and join Zoom meetings via Twilio + Gemini. Multi-turn AI conversations on the phone on behalf of the user.
SKILL.md 표시 중
| name | |
| description | Send WhatsApp messages, list chats, and search history via wacli (local CLI backed by a synced store at ~/.wacli). Unpaired? Run the guided connect flow (scripts/guided_connect.py) from chat — no terminal needed. |
Send messages, list chats, and search history using wacli — a local CLI that syncs a WhatsApp Web session into ~/.wacli/. No third-party service, no API key; the auth flow is a QR-code scan from the user's phone.
wacli chats list --limit 1; if it errors "not authenticated," run the guided connect flow (python3 scripts/guided_connect.py --phone <number>) and relay its protocol lines into chat — the user never opens a terminal. Manual wacli auth in a terminal is the explicit fallback only.brew install openclaw/tap/wacli # one-time install (3rd-party tap, NOT Homebrew-core)
wacli auth # opens a QR for the user to scan from WhatsApp → Linked Devices
openclaw/tap is a third-party Homebrew tap (not Homebrew-core), and wacli stores a WhatsApp Web session locally at ~/.wacli/. Review the tap source before installing if security-sensitive.
The session lives at ~/.wacli/. Stays signed in across reboots until the user revokes the linked device from their phone.
Optional .env settings (label shown in WhatsApp's Linked Devices screen on the user's phone):
WACLI_DEVICE_LABEL=Sutando # any string; appears next to the device in WhatsApp → Linked Devices
WACLI_DEVICE_PLATFORM=CHROME # default per wacli is DESKTOP; CHROME is the fallback if an invalid value is set.
# See wacli's docs (https://github.com/openclaw/wacli) for the full platform-string list.
When the user asks to connect WhatsApp, do NOT tell them to open a terminal. Run the orchestrator and relay its line protocol into the chat:
python3 skills/whatsapp/scripts/guided_connect.py --phone "+14155551234" # preferred
python3 skills/whatsapp/scripts/guided_connect.py # QR fallback
--phone whenever the user's number is known or can be asked for:
it emits PAIR_CODE: XXXX-XXXX, which you relay as text — the user types it
under WhatsApp → Linked devices → "Link with phone number". A QR posted into
the chat cannot be scanned when the chat is open on the same phone.QR_PNG: <path> — attach it to your reply via [file: <path>].
Codes rotate; each new QR_PNG: line supersedes the previous image, so
re-post it. QR_TEXT: <payload> appears instead if the qrcode lib is absent.ALREADY_CONNECTED / CONNECTED both mean the session is live and the
chats probe passed — confirm to the user and offer a closed-loop test send
to a recipient THEY name (wacli refuses self-sends by design).ERROR: <reason> is terminal; relay it honestly. Passkey-gated accounts are
a documented wacli limitation.wacli send text --to "+14155551234" --message "Hello!" # send
wacli send text --to "+14155551234" --message "$(cat draft.txt)" # multi-line via stdin / file
wacli chats list --limit 20 # recent chats
wacli messages search "keyword" --limit 10 # search history
wacli messages list --chat "+14155551234" --limit 20 # read a thread
Phone numbers are in E.164 (+countrycode...). For groups, pass the JID returned by wacli chats list instead of a phone number.
wacli send — this skill itself has no confirm step. Treating the SKILL.md as the confirmation surface would skip the check entirely on direct CLI invocations./tmp/wa-*.txt and pass via --message "$(cat /tmp/wa-X.txt)" — avoids shell-escape issues with quotes and emoji.wacli send text returning success means the message hit WhatsApp's servers, not that the recipient has read it.wacli: not authenticated → run the guided connect flow (scripts/guided_connect.py) and relay its lines; terminal wacli auth only as an explicit fallback. One-time per Mac.wacli: linked device revoked → user revoked the session from their phone. Re-run the guided connect flow.wacli: rate limited → WhatsApp is throttling. Back off ~30s and retry.+ prefix.Synthesizes the proposal in PR #180 by @priyansh4320 (stale + conflicts, never landed) and the wacli reference already documented in CLAUDE.md's "Built-in capabilities" section. Issue #179 (asking for WhatsApp support) was closed 2026-05-16 noting the capability had landed as inline doc.