- chat_bridge: mark_active_tui_session() + get_active_tui_session()
Tracks active TUI session via temp/.active_tui_session.json,
auto-expires after 1 hour (matching Hermes state_meta pattern)
- chat_bridge: inject TUI context when processing coregroup messages
Bot now sees what hmo was discussing in TUI when replying in group
- session_router: record active session ID on every TUI message
Uses _resolve_session() to get the current bound session ID
- Changed from vague '别人对话→ __SILENT__' to explicit 3-condition rule
- LLM response must be ONLY '__SILENT__' (10 chars), nothing else
- Prevents LLM from saying '好的，我输出 __SILENT__' which leaked as chat message
Default LLM behavior is to reply - no prefix needed.
Only the exceptional case (silence) needs a marker.
Updated xmpp_bot.py, MEMORY.md, and protocol doc.
Define how agents should handle messages referencing context
from other sessions (CLI/XMPP/WeChat channel switching).
- SOUL.md: new section 五 on session bridging
- agentmemory: saved as shared architecture rule
- SESSION-BRIDGE-PROTOCOL.md: full protocol doc
Define code+LLM collaboration protocol for group chat participation:
- Code layer: no @mention gate, forward all msgs to LLM
- LLM layer: output __SILENT__ (discard) or __REPLY__ (send)
- Documented in MEMORY.md (LLM prompt) and AgentsMeeting (shared ref)
- Update xmpp_bot.py to remove @mention gate
If xmpp_connected=false, force restart immediately instead of
waiting 10 minutes for message timeout. This catches the most
common failure mode: process alive but XMPP dead.
mohe
hmo