Files
agent-estate-wiki/concepts/tool-calling.md
T
Hermes 341dda95dd stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13)
- skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299)
- runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated
- comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest
- incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised
- incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused)
- 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists)
- log.md addendum + index.md date bump; no page deleted, no secrets written
2026-11-11 03:52:48 +08:00

2.7 KiB
Raw Blame History

title, type, status, created, updated, verified_on, confidence, tags, sources
title type status created updated verified_on confidence tags sources
Tool Calling concept active 2026-07-22 2026-11-11 2026-11-11 high
concept
tool-calling
raw/configs/hermes-config-sanitized.txt

Tool Calling

Idea

How Hermes decides to invoke a tool, and — more specifically for this page — how it detects and stops itself when tool use goes wrong (loops, repeated failures).

How this install implements guardrails

Verified (~/.hermes/config.yaml, tool_loop_guardrails:):

warnings_enabled: true
hard_stop_enabled: false
warn_after:
  exact_failure: 2
  same_tool_failure: 3
  idempotent_no_progress: 2
hard_stop_after:
  exact_failure: 5
  same_tool_failure: 8
  idempotent_no_progress: 5
  • Warnings trigger well before any hard stop (2–3 repeats vs 5–8).
  • hard_stop_enabled: false — Hermes will warn about a stuck tool loop but will not currently force-stop itself. That's a deliberate-looking but consequential setting: a genuinely stuck loop only gets a warning, not an automatic halt.

Why it matters here

This is the mechanism behind runbooks/troubleshoot-tool-loop — that runbook's "agent loops on one tool" symptom is exactly what warn_after/hard_stop_after are meant to catch. With hard-stop disabled, a human (or the messaging integrations) is the actual backstop today.

Re-verified 2026-10-20 — the tool_loop_guardrails: block is byte-for-byte unchanged. Live values in ~/.hermes/config.yaml: warnings_enabled: true, hard_stop_enabled: false, warn_after: {exact_failure: 2, same_tool_failure: 3, idempotent_no_progress: 2}, hard_stop_after: {exact_failure: 5, same_tool_failure: 8, idempotent_no_progress: 5}. 90 days of no drift on this guardrail.

The 2026-10-18 incident is a different loop and the guardrails did not catch it. The degenerate-stream case (see incidents/2026-10-18-degenerate-stream-canned-substitute) was a model output repetition loop — the model repeating itself in the response stream, not a tool call repeating. Hermes's degenerate-stream guard cut it and delivered a canned non-answer, but tool_loop_guardrails (which watches tool calls) never fired. Two separate loop-detection mechanisms exist; do not assume one covers the other.

tool_loop_guardrails re-verified 2026-11-11 — unchanged. warnings_enabled: true, hard_stop_enabled: false, warn_after {exact_failure: 2, same_tool_failure: 3, idempotent_no_progress: 2}, hard_stop_after {exact_failure: 5, same_tool_failure: 8, idempotent_no_progress: 5}. A genuinely stuck tool loop still only ever produces a warning.