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

MESHTASTIC.md: reply to senders as DMs; always respond before starting work #29

Merged
kamilkrzywda merged 2 commits from docs/reply-as-dm into main 2026-09-25 12:52:11 +02:00
Conversation 0 Commits 2 Files Changed 3
+6 -2
3 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 928a1285f4 - Show all commits
CHANGELOG.md
+4
View File
@@ -1,5 +1,9 @@
# Changelog
## v0.12.5 — 2026-09-25 10:45
- Docs (MESHTASTIC.md response protocol): replies to messages from a specific node now go back **as a direct message to that sender's node number** (`to` = the sender's node num), so they surface in the direct conversation thread ("flagged as reply") instead of as new channel posts. Broadcasts (no `to`) are reserved for general announcements such as the hourly weather report. No code changes — `POST /api/send` and the MCP send tool already accept a `to` target; all other rules (owner authority 2594370888, language, confirm-first-then-work, channel pinning, self-echo note, NO_RESPONSE quirk) unchanged.
## v0.12.4 — 2026-09-25 10:17
- Notify forwarder (`ops/forwarder`) now resolves the opencode workspace + session dynamically per request instead of hardcoding them as env defaults: `GET {FORWARDER_API}/api/workspaces` → match by `path == FORWARDER_WORKSPACE_PATH` (fallback `name == "mesh-bot"`, status `ready` preferred when several match) → `GET {proxyPath}/session` → most recently updated session (`time.updated`; first entry if absent). No caching — messages are rare. Fixes lost user messages after an opencode host restart regenerated the workspace UUID (the old hardcoded base URL 404'd on every notify POST).
MESHTASTIC.md
+1 -1
View File
@@ -15,7 +15,7 @@ Rules for how mesh-bot communicates over Meshtastic and how the agent should rea
## Response protocol
- When doing any action triggered by a chat message: **first respond/confirm on the channel, then start the actual work** — so the user gets the fastest possible response.
- Replies to messages received on a channel go back **on that same channel as a broadcast** (no `to`), not as a DM — unless the sender explicitly asks for a private reply.
- Replies to messages from a specific node go back **as a direct message to that sender's node number** (`to` = the sender's node num), so they surface in the direct conversation thread ("flagged as reply") instead of as new channel posts. Broadcasts (no `to`) are reserved for general announcements such as the hourly weather report.
## Channels & sending
package.json
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "mesh-bot",
"version": "0.12.4",
"version": "0.12.5",
"description": "",
"author": "",
"private": true,