Route authorized WhatsApp messages into a local agent CLI.
A free self-hosted command-channel example with a paired WhatsApp number, one Baileys socket, inbox and outbox files, and a Claude CLI route with an acknowledgement fallback.
How it works
The exact pipeline, end to end.
How it actually works
Exactly what it does — and when.
An authorized message arrives through the paired number, is written to the inbox, and is routed to the configured local CLI. When that CLI is unavailable, the channel writes the documented acknowledgement instead of claiming that the requested work completed.
This vs the alternative
Why it's clearly worth it.
The shift it creates
- Remote commands have no small local bridge
- A missing CLI looks like successful execution
- Session and message state are invisible
- Use a number you control for the command channel
- Keep simple inbox and outbox records on your host
- Return a clean acknowledgement when the configured CLI is unavailable
Use it to…
Real ways people put WHATSAPP COMMAND CHANNEL to work.
Send a command from your phone
Route an authorized message from the paired number to the configured local CLI.
Keep a simple message trail
Inspect the inbox and outbox files maintained by the channel.
Handle a missing CLI
Return the documented acknowledgement fallback instead of pretending a task ran.
What's inside
Who it's for
Developers prototyping a mobile command channel
need a small self-hosted example
Claude CLI users
want an authorized message routed to their existing local login
Operators comfortable managing a WhatsApp session
can secure the paired number and host
Questions, answered
Ready to put WHATSAPP COMMAND CHANNEL to work?
Free download · no account needed · yours forever