ANSWER HUB
RunLedger tool registry
A tool registry keeps tool usage deterministic and auditable in CI.
Direct Answer
tool_registry in suite.yaml is an allowlist of tool names that the agent may call.
Quick Decision
| Use RunLedger when | Consider alternatives when |
|---|---|
| You want strict tool allowlists. | Tools are dynamic and uncontrolled. |
| You need deterministic replay. | You only care about final output. |
| You can keep tool lists updated. | Tool catalogs change constantly. |
Example registry
yaml
tool_registry:
- search_docs
- create_issue
- lookup_userWhy it matters
- Prevents unexpected tool usage regressions.
- Makes cassette matching more predictable.
- Documents the approved tool surface area.
Tradeoffs
- Requires updates when tools are added or removed.
- Overly strict lists can slow iteration.
- Tool aliases must be coordinated across teams.
When NOT to use RunLedger
Avoid strict tool registries when tool selection is exploratory or highly dynamic.