configure

/whatsapp-claude-channel:configure — WhatsApp Channel Setup

Manages phone number config and auth state. State lives in ~/.whatsapp-channel/.

Arguments passed: $ARGUMENTS

---

Dispatch on arguments

No args — status and guidance

Give the user a full picture:

1. Phone number — check ~/.whatsapp-channel/.env for WHATSAPP_PHONE_NUMBER. Show set/not-set.

2. Auth state — check ~/.whatsapp-channel/.baileys_auth/creds.json for "registered":true. Show paired/not-paired.

3. Access — run bun run <plugin_root>/src/cli.ts status and show the output.

4. What next — based on state:

   • No phone → Run /whatsapp-claude-channel:configure <phone> (e.g. 919876543210, no +)
   • Phone set but not paired → Restart your session to pair. The pairing code will appear automatically.
   • Paired → Ready. Run /whatsapp-claude-channel:access to manage who can reach you.

Drive toward allowlist lockdown after pairing.

<phone> — save phone number

1. Treat $ARGUMENTS as the phone number (strip +, trim whitespace, digits only).
2. mkdir -p ~/.whatsapp-channel
3. Read existing .env if present. Update/add WHATSAPP_PHONE_NUMBER=<phone>. Preserve other keys.
4. Write back. chmod 600 ~/.whatsapp-channel/.env
5. Confirm and show status.

reset-auth

1. Confirm the user wants to re-pair.
2. rm -rf ~/.whatsapp-channel/.baileys_auth
3. Tell the user: "Auth cleared. Restart your session to re-pair."

clear

Remove WHATSAPP_PHONE_NUMBER= from .env (or delete file if that's the only line).

---

Notes

• Server reads .env at boot — phone number changes need a session restart.
• Access DB (data.db) is re-read on every inbound message — policy changes via /access take effect immediately, no restart needed.
• Only one WhatsApp connection per auth state is allowed. Two instances cause a 440 conflict. Kill stale: pkill -f "bun.*index.ts"