wiki: publish pending edits (2026-10-20)

This commit is contained in:
Tony0410
2026-10-20 18:38:11 +08:00
parent 667ab7f41d
commit fbd4f297eb
46 changed files with 1012 additions and 197 deletions
+16 -2
View File
@@ -3,8 +3,8 @@ title: Tool Calling
type: concept
status: active
created: 2026-07-22
updated: 2026-07-22
verified_on: 2026-07-22
updated: 2026-10-20
verified_on: 2026-10-20
confidence: high
tags: [concept, tool-calling]
sources: [raw/configs/hermes-config-sanitized.txt]
@@ -35,6 +35,20 @@ hard_stop_after:
## 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.
## Related
- [[concepts/persistent-shells]]
- [[runbooks/troubleshoot-tool-loop]]