feat: make DAVE Telegram chat conversational
This commit is contained in:
@@ -1,6 +1,16 @@
|
||||
# Agent Handoff
|
||||
|
||||
Last updated: 2026-07-05
|
||||
Last updated: 2026-07-07
|
||||
|
||||
## DAVE Conversational Telegram Delivery And Web Search
|
||||
|
||||
- Issue #82 tracks operator feedback from 2026-07-07: proactive DAVE messages were too report-like, used visible Markdown markers, arrived as large text blocks, and needed a way to start web searches from chat.
|
||||
- Implementation branch in progress: `codex/issue-dave-conversation-web-search`.
|
||||
- DAVE persona now explicitly prefers live chat style, short natural paragraphs, no visible Markdown syntax, and compact first proactive/presence messages.
|
||||
- Telegram transport has `sendConversation(...)`, which strips visible Markdown syntax for plain-text AI chat and splits large AI/proactive responses into smaller Telegram messages. Handler responses can set `conversation: true`.
|
||||
- Proactive sweep alerts and dynamic presence now use the conversation transport. The DAVE answer, evidence, and tool trace are sent as separate short messages where possible.
|
||||
- The terminal agent has a new read-only `web_search` tool backed by GDELT DOC search. It is bounded by query length, result limit, and time window; it does not provide arbitrary shell/filesystem/secret/network access.
|
||||
- Tests added/updated: Telegram conversation splitting/Markdown cleanup and bounded `web_search` registry behavior.
|
||||
|
||||
## Dynamic DAVE Presence
|
||||
|
||||
|
||||
Reference in New Issue
Block a user