Port from openai/codex#30511: warn against delegating critical-path/coupled work

delegate_task's WHEN NOT TO USE guidance covered mechanical/single-call/
interactive cases but not over-delegation of blocking work. Codex #30511
restored v1 delegation guidance clarifying that requests for depth/research
do not by themselves authorize spawning, and that critical-path, urgent, or
tightly-coupled work should stay on the main rollout.

Adapt that guidance to hermes-agent's delegate_task tool description (static
string, no cache/alternation impact): delegate independent branches, keep the
spine local.
This commit is contained in:
teknium1 2026-06-30 17:02:51 -07:00
parent 20ca2d5759
commit 5fdc65ceb5
No known key found for this signature in database

View file

@ -3185,6 +3185,11 @@ def _build_top_level_description() -> str:
"- Mechanical multi-step work with no reasoning needed -> use execute_code\n"
"- Single tool call -> just call the tool directly\n"
"- Tasks needing user interaction -> subagents cannot use clarify\n"
"- Critical-path, urgent, or tightly-coupled work -> keep it local. A "
"request for depth, research, or investigation does NOT by itself mean "
"delegate: if the work blocks your next step, must interleave with your "
"own reasoning, or is the main deliverable rather than independent side "
"work, do it yourself. Delegate the independent branches, keep the spine.\n"
"- Durable long-running work that must outlive the current turn -> "
"use cronjob (action='create') or terminal(background=True, "
"notify_on_complete=True) instead. Background delegations are NOT "