signal

# Signal Integration

## Overview

This skill provides complete guidance for using OpenClaw's Signal channel (via `signal-cli`). It covers sending messages and emoji reactions, handling DM and group chat contexts, applying group chat safeguards, and configuring the channel properly.

## Important Considerations

- **Number model**: The gateway connects to a *Signal device* (the `signal-cli` account). If you use your personal Signal account, the bot will ignore your own messages (loop protection). Use a **separate bot number** for optimal operation.
- **Group policy**: If `channels.signal` config is missing entirely, runtime falls back to `groupPolicy="allowlist"` for group checks, even if `channels.defaults.groupPolicy` is set.
- **Pairing**: New DM senders receive a pairing code and their messages are ignored until approved (`openclaw pairing approve signal <CODE>`). Codes expire in 1 hour.

## Quick Start

### Sending a simple message
```bash
message action=send channel=signal target="+15551234567" message="Hello from OpenClaw"
```

### Sending a reaction (emoji response to a specific message)
```bash
message action=react channel=signal target="+15551234567" messageId="1737630212345" emoji="🔥"
```

To remove a reaction:
```bash
message action=react channel=signal target="+15551234567" messageId="1737630212345" emoji="🔥" remove=true
```

### Group reactions
```bash
message action=react channel=signal target="signal:group:<groupId>" targetAuthor="uuid:<sender-uuid>" messageId="1737630212345" emoji="✅"
```

## Group Chat Safeguards

When participating in Signal group chats (multiple participants), follow these rules:

1. **Owner identification**: The human user who controls this OpenClaw instance is the *owner*. Their contact info (phone number, etc.) is stored in OpenClaw configuration as the primary controller. (In a default setup, this is the user listed in `USER.md`.)

2. **Non-owner requests for destructive actions**: If a non-owner asks you to perform a dest...