open-webui / open-webui/computer

Feat: improve Signal. Message handling / implement Signal message editing

Open
#160 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
569
Forks
79
PR merge metrics
No merged PRs in 30d

Description

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:
https://github.com/Georg311/computer/commit/4a06ec404d2aa6f032ba254729e809d1d2b899dc

With 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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with cptr/utils/adapters/signal.py and cptr/utils/bridge.py, then inspect the linked implementation commit. Check how Signal's signal-cli edit_timestamp is handled and how bridge edit failures are logged. Done means Signal edits update messages in place without duplicates, with the existing Telegram behavior preserved; Discord remains unverified by the report.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.