mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-21 16:18:55 +00:00
a35bc81b3f
The five Honcho tool schemas had overlapping/misleading descriptions, making it hard for the model to pick the right one, plus two concrete correctness bugs: - honcho_context advertised an 'Optional focus query' parameter that the dispatch never read. The model could pass query= expecting filtering that never happened. Remove the dead parameter; honcho_context is an honest no-query snapshot. Focused retrieval now lives in honcho_search (see prior commit). - honcho_conclude's peer param was described as 'Peer to query' — wrong; it's the peer the conclusion is ABOUT. Corrected. Rewrite all five descriptions to give each tool a distinct mental model and cross-reference siblings: profile = read/write the compact card (cheapest, no query, no LLM) search = find what was actually said, ranked, cross-session (cheap, no LLM) reasoning= ask a question, get a synthesized answer (the only LLM tool; expensive) context = a fixed session snapshot (no query, no LLM) conclude = write a durable fact to the profile Addresses the honcho_context query param half of #29402 (see PR notes for the divergence from that issue's proposed wire-through approach). |
||
|---|---|---|
| .. | ||
| 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 | ||