Release notes

HOL Guard v3.60.0a109

Preview

HOL Guard v3.60.0a109, released November 17, 2026, is a preview release with 1 addition, 2 improvements, 7 fixes and 3 other changes across 12 merged pull requests. Highlights: Explain MCP tool approvals in plain English; Move the resident client pool into its own module.

Changes since the previous release on this channel: alpha/v3.60.0a108alpha/v3.60.0a109

1 added · 2 improved · 7 fixed · 3 other

Published Original GitHub release for alpha/v3.60.0a109

Key facts

Version
v3.60.0a109
Channel
Preview
Published
Previous release
alpha/v3.60.0a108
Merged pull requests
12

Documented changes

13 typed entries

Verified contributors

Credits being verified. Attribution coverage is in progress.

Attribution coverage

attribution in progress; history inventory partial.

Scope

Guard v3.60.0a109 is a preview release published 2026-11-17. Upstream documents: Guard 3.60.0a109 is an opt-in prerelease cut from 43812dc. Stable installations remain on the stable channel. 12 commits • 12 merged pull requests • 1 contributor since Guard 3.60.0a108. Its comparison base is alpha/v3.60.0a108. It includes 12 verified contribution deliveries with public evidence links. Attribution for this release is being verified.

Changes

Added

1
  • guardExplain MCP tool approvals in plain English (#7905) Evidence for this change
    • MCP tool approvals now read in words. The review title, queue rows and card say who is calling which service and what the call does ("ZCode wants to search for tools in Composio", with the apps named) instead of a JSON…
    • Each call gets an effect label read from the tool name only: looks things up, changes something, sends something, deletes something, runs code, or changes a connection. The card says the label comes from the name and…
    • Text the agent wrote about its own call (thought, use_case) is shown as a quote attributed to the agent, with control and bidi characters removed. It never reaches the title, the effect or the summary. A string…

Improved

2

Fixed

7

Other changes

3
  • Guard 3.60.0a109 is an opt-in prerelease cut from 43812dc. Stable installations remain on the stable channel. 12 commits • 12 merged pull requests • 1 contributor since Guard 3.60.0a108. Evidence for this change
  • cigarAdd general-savings benchmark tables and the rig scripts behind them (#7912) Evidence for this change
  • gauntletBind the built native runtime for Linux lane preflight (#7915) Evidence for this change
    • Merged pull request #7915: ci(gauntlet): bind the built native runtime for Linux lane preflight
    • Merged pull request #7906: fix(guard): tell the agent to pass the signed review link on whole (#7906)
    • Merged pull request #7910: fix(guard): keep the resident's lease when a closing owner asks it a question (#7910)
    • Merged pull request #7908: fix(guard): let a custom MCP tool allow answer the unreviewed-tool setting (#7908)
    • Merged pull request #7911: fix(guard): treat node --version as a version check, not a vulnerable launch (#7911)
    • Merged pull request #7912: docs(cigar): add general-savings benchmark tables and the rig scripts behind them (#7912)
    • Merged pull request #7905: feat(guard): explain MCP tool approvals in plain English (#7905)
    • Merged pull request #7916: fix(guard): keep the daemon answering under a burst of thousands of hooks
    • Merged pull request #7919: refactor(guard): move the resident client pool into its own module
    • Merged pull request #7920: fix(cigar): skip project notes on messages Claude Code writes itself
    • Merged pull request #7718: refactor(guard): move harness probes, lookups and the Cline canary into the native runtime (#7718)
    • Merged pull request #7903: fix(guard): let PostToolUse honor the approval that admitted the call (#7903)

Upgrade and compatibility

None documented.

Compare with the previous release

Predecessor on the same channel: alpha/v3.60.0a108

Verified contributors

Credits derive from public pull-request authorship, verified commit authorship, or verified co-authorship — never from thanks text or release metadata. Each distinct contributor is listed once; the evidence ledger paginates every published credit record.

Contributors

Evidence ledger12 credits