Hermes Agent is not reliably delegating to sub-agents
A setup connected to Deepseek through a direct API is not delegating tasks reliably. The main agent used in Telegram chat runs on Deepsek V4 Pro.
Three were created: for coding work, config-agent for changing Hermes settings, and research-agent for research. The use .
The problem is that the main often handles tasks by itself instead of passing them to the right sub-agent. Memory is being used through menmosney, and the main agent has been told to remember to use the , but the delegation still happens inconsistently.
Key points
- The main Telegram-facing agent uses Deepsek V4 Pro.
- There are three : , config-agent, and research-agent.
- The run on .
- The often does the work itself instead of delegating.
- Memory and reminders have not made delegation consistent.