mirror of
https://github.com/open-webui/computer.git
synced 2026-11-05 01:17:24 +00:00
[GH-ISSUE #160] Feat: improve Signal. Message handling / implement Signal message editing #84
Labels
No labels
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/computer#84
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Georg311 on GitHub (Jul 21, 2026).
Original GitHub issue: https://github.com/open-webui/computer/issues/160
The api documentation on the Signal Rest api bridge was quite sparse, but it is possible to edit Signal messages via the Rest api bridge
Implementation can be seen here:
github.com/Georg311/computer@4a06ec404dWith this commit it's possible to send the messages the same in Signal as on other platforms by starting with thinking... And then editing the message to the actual thing.
The fix consists of two changes
cptr/utils/adapters/signal.py — Added edit() method using signal-cli's edit_timestamp field (so messages can be edited in-place instead of sending duplicates)
cptr/utils/bridge.py — Better error logging and early return on edit failures across all platforms
The bridge.py fix was necessary to prevent the message from being duplicated at the end of the message.
I've tried the fix with telegram and Signal, i don't have a discord Account to test there, but it should work as well
@owui-terminator[bot] commented on GitHub (Jul 21, 2026):
🔍 Related Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
This is the only clearly related Signal integration issue in the repo. It covers the Signal REST API bridge used by this feature, so it is the most likely predecessor/adjacent issue for message handling changes even though it focuses on connectivity rather than editing.
by Georg311
💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
@Georg311 commented on GitHub (Jul 21, 2026):
This issue was the previous workaround to get Signal messages to work at all