Why does Signal setup take so much longer than Telegram?

Signal doesn't have an official bot API. OpenClaw uses signal-cli, a command-line client that registers a real phone number with Signal's network. This requires getting a dedicated phone number, installing signal-cli, and registering via SMS verification — more steps than Telegram's simple token system.

Can I use my existing personal Signal number?

No — strongly advised against it. signal-cli and the Signal app cannot share the same number simultaneously. Using your personal number for the bot would disconnect your Signal app. Always get a dedicated number (Google Voice, Twilio, or prepaid SIM) specifically for the agent.

Are messages end-to-end encrypted?

Yes. Signal's end-to-end encryption applies to all messages, including those sent through signal-cli. Your messages are encrypted between your phone and the agent's Signal number — not even Signal's servers can read them. This makes Signal the most private OpenClaw channel available.

Signal – HowOpenClaw

Signal offers the strongest privacy guarantees of any OpenClaw channel. Messages remain end-to-end encrypted throughout. No metadata exposed to third parties, no unofficial API emulation.

The tradeoff: setup is the most involved of any channel. Plan 30–60 minutes for your first attempt.

Get a dedicated phone number

Do not use your personal Signal account. Signal links your account to your phone number, and using your personal number creates conflicts when the agent sends messages on your behalf.

Get a separate number for your agent:

Google Voice (free, US only)
Twilio (+$1/month)
Prepaid SIM

Install signal-cli

signal-cli is the command-line Signal client that OpenClaw uses.

macOS:

brew install signal-cli

Linux:

# Download the latest release from GitHub
wget https://github.com/AsamK/signal-cli/releases/latest/download/signal-cli-*.tar.gz
tar -xzf signal-cli-*.tar.gz
sudo mv signal-cli-*/bin/signal-cli /usr/local/bin/

Verify:

signal-cli --version

Register your number

# Register with your dedicated number
signal-cli -u +15559876543 register

# You'll receive a verification code via SMS
signal-cli -u +15559876543 verify 123456

# Trust your own number
signal-cli -u +15559876543 updateAccount

Configure OpenClaw

{
  "channels": {
    "signal": {
      "enabled": true,
      "signalCliPath": "/usr/local/bin/signal-cli",
      "phoneNumber": "+15559876543",
      "dmPolicy": "allowlist",
      "allowedContacts": [
        "+15551234567",
        "+15559999999"
      ],
      "groupPolicy": "never"
    }
  }
}

Restart and test

openclaw gateway restart

Send a test message from your personal Signal account to the agent's number. Watch logs as you test:

openclaw logs --follow | grep signal

Group Chat Limitations

Signal groups work differently from other platforms, and the integration has less mature group support. Group messages may not route correctly in all configurations.

For team use cases, Slack or Telegram are more reliable choices. Use Signal for one-on-one personal communication where privacy is the priority.

Why Signal Complexity Is Worth It

For the right use case — private, sensitive communications — Signal's end-to-end encryption means:

Messages aren't readable by OpenClaw's infrastructure
No metadata exposed to Apple, Google, or Meta
No corporate server storing your conversation history

If you're using your agent for anything sensitive (medical, legal, financial), Signal is the right channel.

Troubleshooting

Registration fails: Check that your number is in E.164 format (+15559876543) and that you're receiving SMS.

Agent doesn't receive messages: Verify signalCliPath points to your actual installation, and that the phone number in config matches your registered number exactly.

Session errors: Re-register the number if signal-cli reports authentication failures:

signal-cli -u +15559876543 register --force

Something not working?

Check the troubleshooting guide for common issues with gateway startup, channel connections, and automations.