OpenCode/MeshBot
2
0
Fork 0
Code Issues Pull Requests Actions Activity

mesh: replace notify webhook with in-process opencode notifier; drop forwarder service

Browse Source
This commit is contained in:
kamilkrzywda
2026-09-25 14:14:37 +00:00
parent 7d7c569d08
commit 5eb1a79e70
8 changed files with 77 additions and 377 deletions
Download Patch File Download Diff File Expand all files Collapse all files
MESHTASTIC.md
+1 -1
View File
@@ -25,4 +25,4 @@ Rules for how mesh-bot communicates over Meshtastic and how the agent should rea
## Notifications (mesh → agent)
- RX text on the notify channel (`MESH_NOTIFY_CHANNEL`, default 3) triggers an outbound webhook POST `{text, from}` to `MESH_NOTIFY_URL` (host forwarder :4097 → opencode session). Messages from our own node are never notified (self-echo filter, v0.11.2).
- RX text on the notify channel (`MESH_NOTIFY_CHANNEL`, default 3) is pushed in-process to the live opencode session by `OpencodeService` (workspace/session resolved per request from the opencode API; disabled without `OPENCODE_USER`/`OPENCODE_PASS`). Messages from our own node are never notified (self-echo filter, v0.11.2).