Signal 提及占位符  替换为可读 @uuid/@phone(PR #2013)
解决 Signal 消息中 mention 被解析成不可读字符导致误解语义的问题:按 mentions 元数据逆序替换为可读标识。
GITHUBDiscovered 2026-02-13Author alexgleason
Prerequisites
- Signal channel integration is enabled and mention-heavy messages are part of your workflow.
- You can test with at least two mentions in one message to validate index handling.
Steps
- Upgrade to runtime containing PR #2013 and restart gateway.
- Send Signal test message with multiple mentions and mixed plain text.
- Inspect parsed message text and confirm placeholder characters are replaced with @uuid/@phone.
- Verify replacement order is reverse-index to avoid offset shift corruption.
- Run a regression where no mentions exist to ensure plain text path remains unchanged.
Commands
openclaw gateway statusopenclaw gateway restartopenclaw statusVerify
Mentioned messages are consistently human-readable and no longer rendered as replacement glyphs in assistant context.
Caveats
- @uuid/@phone is a technical identifier, not always a friendly display name.
- Different Signal bridge versions may expose mention metadata differently(需验证)。
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗