hermes - 💡(How to fix) Fix Subagent tool delegation inconsistent — file/terminal tools missing for children despite toolsets parameter [1 pull requests]

Bug: Subagent tool delegation inconsistent

Summary

When spawning subagents via delegate_task with toolsets=['file', 'terminal'], the child agents sometimes report "Tool read_file does not exists" / "Tool terminal does not exists" despite the toolsets parameter being correctly set. The behavior depends on the parent agent's context and model.

Observations

Error message

Tool read_file does not exists.
Tool terminal does not exists.
Tool search_files does not exists.
Tool write_file does not exists.

Reproduction steps

1. Create a cron job (or any session where parent runs on DeepSeek)
2. In the cron job, call delegate_task with toolsets=['terminal', 'file']
3. The subagent reports that read_file, terminal, search_files, write_file don't exist

Root cause hypothesis

From the delegate_tool.py docs:

"Explicit child toolsets are intersected with the parent's toolsets (must not gain tools the parent lacks)."

If the intersection logic strips file/terminal tools when the parent (DeepSeek in cron context) doesn't advertise those toolset capabilities, the child never gets them regardless of the toolsets parameter or the delegation.default_toolsets config.

The inconsistency in user sessions (~80% success rate) suggests a race condition or caching issue — possibly related to the _last_resolved_tool_names save point noted in the code:

"Save parent tool names BEFORE building children (because _build_child_agent calls AIAgent() which overwrites model_tools._last_resolved_tool_names)."

Expected behavior

When toolsets=['file', 'terminal'] is explicitly passed to delegate_task, the child agent should reliably have read_file, search_files, write_file, and terminal tools available, regardless of the parent agent's model or runtime context.

Environment

• Hermes Agent version: current main branch
• Config: delegation.default_toolsets: ['terminal', 'file', 'web']
• Subagent model: custom provider Blaze (qwen3.6-plus at blazeai.boxu.dev)
• Deployment: local Linux server, Telegram gateway + cron scheduler