Signal¶
Signal uses an authenticated signal-cli-rest-api server and the shared gateway
bridge.
Server Setup¶
Run and authenticate signal-cli-rest-api separately, then record:
- REST API base URL, for example
http://127.0.0.1:8080 - Signal account or number registered in that server
The gateway stores the REST URL and account in instance_config.yaml. Keep any
server-side credentials outside the agent process.
Onboarding Flags¶
.venv/bin/python assistant_cli.py onboard \
--enable-signal \
--signal-base-url http://127.0.0.1:8080 \
--signal-account +15550001111 \
--signal-allow-sender-id +15551234567
For groups:
--signal-allow-group-id group.signal \
--signal-group-policy mention \
--signal-mention-marker @Lisa
Inbound Identity¶
Direct Signal sessions bind to sourceUuid when available, otherwise the E.164
source phone number. Rejected sender logs include newuser_target=... for admin
onboarding.
Proactive Delivery¶
If Signal should receive proactive agent messages:
--default-delivery-channel signal \
--default-delivery-chat-id +15551234567
For groups, use the configured Signal group id as the chat id.
Verification¶
- Start signal-cli-rest-api and confirm the account is registered.
- Start the gateway with Signal enabled.
- Send a direct Signal message from an allowed sender.
- Confirm the gateway logs the inbound sender id.
- Confirm the agent replies through Signal.
- Test a group only after
allowed_group_idsand mention policy are configured.
Troubleshooting¶
- Startup fails: verify
interactive_apps.plugins.builtin.signal.settings.base_urlandaccount. - Direct messages are ignored: check
allowed_sender_idsor onboard the user with/user. - Groups are ignored: configure
allowed_group_idsand mention markers. - Attachments are missing: check the signal-cli-rest-api attachment settings.