#Openclaw signal upload
1 messages · Page 1 of 1 (latest)
Yes — Signal supports media in OpenClaw now.
- Inbound: Signal attachments can be downloaded and passed to the agent.
- Outbound: the agent can send media/attachments back through Signal.
- Limit:
channels.signal.mediaMaxMbcontrols the inbound/outbound cap, default 8 MB. - Targets: DMs use
signal:+1555.../ E.164 oruuid:<id>; groups usesignal:group:<groupId>.
Docs: https://docs.openclaw.ai/channels/signal
Example agent ask:
“Send this image file to Signal +15551234567”
or via tool-style send, it can use media, path, or filePath as the attachment source, as long as the file is inside the agent’s allowed media/workspace access.
how to enable the outbound capability?
First check your version: openclaw --version — if this doesn’t work, version matters.
There isn’t a separate channels.signal.outbound toggle. Signal outbound is enabled when Signal is configured; for agent-initiated sends, make sure the agent has the message tool:
{
channels: {
signal: {
enabled: true,
account: "+15551234567",
cliPath: "signal-cli",
mediaMaxMb: 25
}
},
tools: {
profile: "coding",
alsoAllow: ["group:messaging"] // or ["message"]
}
}
If you already use tools.allow, add message / group:messaging there instead — don’t use allow and alsoAllow in the same scope.
Restart + test:
openclaw gateway restart
openclaw channels status --probe
openclaw message send --channel signal \
--target +15557654321 \