WhatsApp reply_prefix config setting ignored by bridge
Cluster 116059. Data as of
Nothing open on GitHub. Fix merged in #116783 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #116783. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116783. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug was identified where the reply_prefix setting configured in config.yaml was not being passed through to the WhatsApp bridge. Multiple fix attempts address propagating this value correctly, including handling an empty string to disable the prefix.
Open issues0
Open PRs0
Fixes on record
-
#116783 fix(whatsapp): reply_prefix from config.yaml reaches the bridge, including the empty disable value (#116059, salvage #116067)
files:
plugins/platforms/whatsapp/adapter.py,tests/gateway/test_adapter_settings_scoped_precedence.py,tests/gateway/test_whatsapp_reply_prefix.py
2 PRs closed without merging
From the close comments: duplicate 1 · merged via another change 1
Closed issues · 1
- Closed#116059[Bug]: WhatsApp reply_prefix set in config.yaml never reaches the bridge (documented setting is ignored)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #116783
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 20 Sep 2026