calciforge/signal-config-example.toml at main · bglusman/calciforge · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
# Signal Channel Configuration Example for Calciforge
#
# Add this to your ~/.config/calciforge/config.toml to enable Signal support.
# Signal uses the same webhook receiver pattern as WhatsApp.

[[channels]]
kind = "signal"
enabled = true

# OpenClaw or ZeroClaw gateway endpoint that owns the Signal session
# This is where Calciforge will POST replies via /tools/invoke
zeroclaw_endpoint = "http://127.0.0.1:18789"

# Bearer token for the OpenClaw or ZeroClaw gateway
zeroclaw_auth_token = "REPLACE_WITH_AUTH_TOKEN"

# HTTP address to listen on for incoming webhooks from OpenClaw
# Default: 0.0.0.0:18796
webhook_listen = "0.0.0.0:18796"

# URL path for incoming webhooks
# Default: /webhooks/signal
webhook_path = "/webhooks/signal"

# Optional: HMAC-SHA256 secret for webhook signature verification
# webhook_secret = "your-shared-secret"

# Allowed sender phone numbers in E.164 format
# Must match identity aliases with channel = "signal"
allowed_numbers = ["+15555550001"]

# -----------------------------------------------------------------------------
# Corresponding identity configuration example:
# -----------------------------------------------------------------------------

[[identities]]
id = "operator"
display_name = "Operator"
role = "admin"
aliases = [
    { channel = "signal", id = "+15555550001" },
    { channel = "telegram", id = "12345678" },
]

[[routing]]
identity = "operator"
default_agent = "librarian"
allowed_agents = ["librarian", "max", "qwen"]