Signal (signal-cli)
Status: external CLI integration. Gateway talks tosignal-cli over HTTP JSON-RPC + SSE.
Quick setup (beginner)
- Use a separate Signal number for the bot (recommended).
- Install
signal-cli(Java required). - Link the bot device and start the daemon:
signal-cli link -n "Clawdia"
- Configure Clawdia and start the gateway.
What it is
- Signal channel via
signal-cli(not embedded libsignal). - Deterministic routing: replies always go back to Signal.
- DMs share the agent’s main session; groups are isolated (
agent:<agentId>:signal:group:<groupId>).
Config writes
By default, Signal is allowed to write config updates triggered by/config set|unset (requires commands.config: true).
Disable with:
The number model (important)
- The gateway connects to a Signal device (the
signal-cliaccount). - If you run the bot on your personal Signal account, it will ignore your own messages (loop protection).
- For “I text the bot and it replies,” use a separate bot number.
Setup (fast path)
- Install
signal-cli(Java required). - Link a bot account:
signal-cli link -n "Clawdia"then scan the QR in Signal.
- Configure Signal and start the gateway.
channels.signal.accounts with per-account config and optional name. See gateway/configuration for the shared pattern.
External daemon mode (httpUrl)
If you want to managesignal-cli yourself (slow JVM cold starts, container init, or shared CPUs), run the daemon separately and point Clawdia at it:
channels.signal.startupTimeoutMs.
Access control (DMs + groups)
DMs:- Default:
channels.signal.dmPolicy = "pairing". - Unknown senders receive a pairing code; messages are ignored until approved (codes expire after 1 hour).
- Approve via:
clawdia pairing list signalclawdia pairing approve signal <CODE>
- Pairing is the default token exchange for Signal DMs. Details: Pairing
- UUID-only senders (from
sourceUuid) are stored asuuid:<id>inchannels.signal.allowFrom.
channels.signal.groupPolicy = open | allowlist | disabled.channels.signal.groupAllowFromcontrols who can trigger in groups whenallowlistis set.
How it works (behavior)
signal-cliruns as a daemon; the gateway reads events via SSE.- Inbound messages are normalized into the shared channel envelope.
- Replies always route back to the same number or group.
Media + limits
- Outbound text is chunked to
channels.signal.textChunkLimit(default 4000). - Optional newline chunking: set
channels.signal.chunkMode="newline"to split on each line before length chunking. - Attachments supported (base64 fetched from
signal-cli). - Default media cap:
channels.signal.mediaMaxMb(default 8). - Use
channels.signal.ignoreAttachmentsto skip downloading media. - Group history context uses
channels.signal.historyLimit(orchannels.signal.accounts.*.historyLimit), falling back tomessages.groupChat.historyLimit. Set0to disable (default 50).
Typing + read receipts
- Typing indicators: Clawdia sends typing signals via
signal-cli sendTypingand refreshes them while a reply is running. - Read receipts: when
channels.signal.sendReadReceiptsis true, Clawdia forwards read receipts for allowed DMs. - Signal-cli does not expose read receipts for groups.
Reactions (message tool)
- Use
message action=reactwithchannel=signal. - Targets: sender E.164 or UUID (use
uuid:<id>from pairing output; bare UUID works too). messageIdis the Signal timestamp for the message you’re reacting to.- Group reactions require
targetAuthorortargetAuthorUuid.
channels.signal.actions.reactions: enable/disable reaction actions (default true).channels.signal.reactionLevel:off | ack | minimal | extensive.off/ackdisables agent reactions (message toolreactwill error).minimal/extensiveenables agent reactions and sets the guidance level.
- Per-account overrides:
channels.signal.accounts.<id>.actions.reactions,channels.signal.accounts.<id>.reactionLevel.
Delivery targets (CLI/cron)
- DMs:
signal:+15551234567(or plain E.164). - UUID DMs:
uuid:<id>(or bare UUID). - Groups:
signal:group:<groupId>. - Usernames:
username:<name>(if supported by your Signal account).
Configuration reference (Signal)
Full configuration: Configuration Provider options:channels.signal.enabled: enable/disable channel startup.channels.signal.account: E.164 for the bot account.channels.signal.cliPath: path tosignal-cli.channels.signal.httpUrl: full daemon URL (overrides host/port).channels.signal.httpHost,channels.signal.httpPort: daemon bind (default 127.0.0.1:8080).channels.signal.autoStart: auto-spawn daemon (default true ifhttpUrlunset).channels.signal.startupTimeoutMs: startup wait timeout in ms (cap 120000).channels.signal.receiveMode:on-start | manual.channels.signal.ignoreAttachments: skip attachment downloads.channels.signal.ignoreStories: ignore stories from the daemon.channels.signal.sendReadReceipts: forward read receipts.channels.signal.dmPolicy:pairing | allowlist | open | disabled(default: pairing).channels.signal.allowFrom: DM allowlist (E.164 oruuid:<id>).openrequires"*". Signal has no usernames; use phone/UUID ids.channels.signal.groupPolicy:open | allowlist | disabled(default: allowlist).channels.signal.groupAllowFrom: group sender allowlist.channels.signal.historyLimit: max group messages to include as context (0 disables).channels.signal.dmHistoryLimit: DM history limit in user turns. Per-user overrides:channels.signal.dms["<phone_or_uuid>"].historyLimit.channels.signal.textChunkLimit: outbound chunk size (chars).channels.signal.chunkMode:length(default) ornewlineto split on newlines before length chunking.channels.signal.mediaMaxMb: inbound/outbound media cap (MB).
agents.list[].groupChat.mentionPatterns(Signal does not support native mentions).messages.groupChat.mentionPatterns(global fallback).messages.responsePrefix.
