Tianyi Cui
a7a5be1703
Run the dsh-archive-agent-notes audit over every active Agent Note on current master, judging each record by whether its rationale still guides work rather than by size or age. - Archive 453 implemented bilingual triplets (417,882 English words): completed UI chrome, narrow adapters, closed bug fixes, implementation walkthroughs whose package READMEs, docs pages, generators, or successor notes now carry the useful behavior, and 51 records fully superseded by a later active note. Keep 201 implemented notes whose ownership rules, negative guarantees, durable or wire semantics, security rules, reintroduction conditions, or still-tempting rejected alternatives remain useful. - Reject 7 proposals whose premise is gone or whose work shipped in amended form under other records; delete 2 rejected notes that no longer prevent a plausible mistake. - Retarget every remaining inbound link to the archived path, and repair active prose that named an archived record as the owner of a live fact: parenthetical citations drop, ownership sentences redirect to the README, docs page, or active note that states the fact, and history citations say so. Chinese files link the English archived path because the pairing gate treats the frozen tree as outside the bilingual corpus. - Seal 1,359 new frozen artifacts; existing seals are unchanged and outbound links from archived notes are neither inspected nor repaired. - Regenerate docs/config-catalog.md after the hook-bridge comment edits shifted two source line numbers.
description, kind
| description | kind |
|---|---|
| Package map for the loop-hygiene guard family: the advisory repeat-tool reminder and the per-call tool-call timeout policy, for users and maintainers choosing or composing the guards. | package-group |
guard/ — loop-hygiene guard family
English | 中文
Summary
The guard/ group keeps the agent loop productive by watching for two common failure patterns. repeat-tool-reminder notices when the model repeats the exact same tool call and reminds it to change approach or finish, so a stuck loop stops burning time and tokens. timeout-policy puts a time limit on tool calls that declare one, so a hung call returns a clear timed-out error to the model instead of stalling the session. Both ship enabled in the dsh base bundle; a composition can tune or remove them.
Table of Contents
Packages
Two small plugins cover the two patterns; each README below explains when to keep, tune, or remove it.
| Package | What it provides |
|---|---|
repeat-tool-reminder/ |
Reminds the model when it repeats the same tool call, so it changes approach or finishes |
timeout-policy/ |
Times out tool calls that declare a limit, so the model gets a clear error instead of waiting forever |
Related documentation
Start with the tools subsystem reference for the tool-call pipeline, then the reminder's configuration and the timeout-library decision behind the policy.
- Tools subsystem reference — the tool-call pipeline and decisions both guards build on.
- Generated configuration catalog — every accepted field of the repeat-call reminder.
- Timeout deadline library Agent Note — the timing/termination split
timeout-policyenforces.
Dev Note
Working context for maintainers — click to expand
None.