+ iHàjž ãó\€Rt^RIHt^RIHtHtHtHt]!R04t RRlt RRlt Rt R #) uWhat a finite one-shot session (``hermes chat -q`` / ``--oneshot``, ``hermes -z``) does NOT do. A one-shot run has no later session in its HERMES_HOME to learn for: the process answers one query and exits. The interactive self-improvement loop is pure overhead there, and a measured one — across 21 one-shot benchmark trajectories the agent authored 7 new skills and patched a bundled one mid-task, 37 of ~215 tool calls were ``skill_view``/``skill_manage``, and skill text was 34% of every tool-result byte fed back into context. Three rules follow, all keyed on the same session marker the approval gate and the delegation dispatcher already read (``HERMES_SINGLE_QUERY_SESSION``), so interactive sessions are untouched: * ``skill_manage`` is not offered (``skills_list``/``skill_view`` stay: reading a domain skill can still win); * the ## Skills prompt drops the "record it / patch it / offer to save" coaching and the "load process skills even for tasks you already know" push, keeping only "load a skill when it adds knowledge you lack"; * delegation is capped per session (``delegation.oneshot_max_children``): subagents each re-pay a cold system prompt and re-explore the repo, and the observed spawns were mostly "independent review of my own work" rather than parallel work. )Ú annotations)ÚAnyÚDictÚIterableÚListÚ skill_managecó€V^8„dQhRR/#)éÚreturnÚbool©)Úformats"Úr1s:ðñõ #ç,Ó,á  .Ð!1Ó2ÐõPõ,cðLòr