mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-22 16:25:58 +00:00
73d5c896ee
Two mention-tracking gaps around thread parents (#24848): 1. When a thread PARENT @-mentioned the bot (e.g. '<@bot> check this and ask me before running'), a later bare reply like 'run' fell through every wake check if the mention event predated this process (restart) — _mentioned_threads is in-memory only. Add a 5th wake check that fetches the parent text (with the bot mention preserved via strip_bot_mention=False) and wakes when the parent addressed the bot, registering the thread so later replies skip the fetch. 2. A TOP-LEVEL @mention starts a thread (session keying falls back to the message ts), but only the raw event thread_ts was registered in _mentioned_threads — so replies to a top-level mention did not auto-trigger. Register the session-scoped thread_ts instead. _fetch_thread_parent_text reuses the shared thread-context cache (raw payloads) so the parent check costs at most one conversations.replies call per thread; _register_mentioned_thread centralizes the bounded-set eviction. Salvaged from #24848 by @kaiyisg, rebased onto the extracted _should_wake_on_unmentioned_message helper. |
||
|---|---|---|
| .. | ||
| browser | ||
| context_engine | ||
| cron_providers | ||
| dashboard_auth | ||
| disk-cleanup | ||
| google_meet | ||
| hermes-achievements | ||
| image_gen | ||
| kanban | ||
| memory | ||
| model-providers | ||
| observability | ||
| platforms | ||
| security-guidance | ||
| spotify | ||
| teams_pipeline | ||
| video_gen | ||
| web | ||
| __init__.py | ||
| plugin_utils.py | ||