let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: drop gateway ipc remnants

Browse Source
This commit is contained in:
Peter Steinberger
2025-12-09 20:21:41 +00:00
parent 131864b940
commit a76d00a08e
8 changed files with 14 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/surface.md
View File

@@ -15,5 +15,5 @@ Goal: make replies deterministic per channel while keeping one shared context fo
- **WebChat:** Always attaches to `main`, loads the full Tau transcript so desktop reflects cross-surface history, and writes new turns back to the same session.
- **Implementation hints:**
- Set `Surface` in each ingress (WhatsApp gateway, WebChat bridge, future Telegram).
- Keep routing deterministic: originate → same surface. Use IPC/web senders accordingly.
- Keep routing deterministic: originate → same surface. Use the gateway WebSocket for sends; avoid side channels.
- Do not let the agent emit “send to X” decisions; keep that policy in the host code.