Release notes
HOL Guard v3.60.0a112
PreviewHOL Guard v3.60.0a112, released November 17, 2026, is a preview release with 1 addition, 6 fixes and 2 other changes across 8 merged pull requests. Highlights: Start agents from a command, define their work, and keep them out of folders; Let Watch harness hooks through while the daemon is down, and file Claude Code hooks as.
1 added · 6 fixed · 2 other
Key facts
- Version
- v3.60.0a112
- Channel
- Preview
- Published
- Previous release
- alpha/v3.60.0a111
- Merged pull requests
- 8
Documented changes
9 typed entries
Verified contributors
2 verified contributors · 8 credits
Attribution coverage
attribution complete; history inventory partial.
Install
Scope
Guard v3.60.0a112 is a preview release published 2026-11-17. Upstream documents: Guard 3.60.0a112 is an opt-in prerelease cut from d903a54. Stable installations remain on the stable channel. 8 commits • 8 merged pull requests • 2 contributors since Guard 3.60.0a111. Its comparison base is alpha/v3.60.0a111. It includes 8 verified contribution deliveries with public evidence links.
Changes
Added
1- swarmStart agents from a command, define their work, and keep them out of folders (#7945) Evidence for this change
Fixed
6- guardLet Watch harness hooks through while the daemon is down, and file Claude Code hooks as Claude Code's (#7940) Evidence for this change
- daemon-manageDon't count another program's thread as a running daemon (#7932) Evidence for this change
- guardRecord why every daemon exit happened (#7930) Evidence for this change
- The daemon records its own exit.
daemon-servewrites anexitinglifecycle event with a reason for SIGTERM (signal_term), the launcher's input closing (launcher_input_closed), the listener ending or failing… - A start that never published says why.
start_failedrecordslaunch_input_unreadable,launch_config_invalid,launch_config_mismatch,listen_failed,listener_address_unavailableorpublish_failed. A… - Every retirement names who asked.
retire_all,retire_pid, the orphan sweeps, stale-runtime retirement and an abandoned launch each writeretirement_requestedwith a reason and the retiring process's pid and…
- The daemon records its own exit.
- guardRetire daemons of deleted homes and leftover relays, and sweep abandoned temp files (#7941) Evidence for this change
- cigarCap advisory prompt workers (#7949) Evidence for this change
- Cap concurrent CIGAR prompt warm-up and lookup workers across all workspaces.
- Reserve advisory capacity before waiting on the CIGAR lane so a full budget returns promptly.
- Keep overload responses recognizable to clients so rejected hooks do not trigger recovery work.
- guardTell the agent an allowed script changed instead of saying it was never set up (#7944) Evidence for this change
Other changes
2- Guard 3.60.0a112 is an opt-in prerelease cut from
d903a54. Stable installations remain on the stable channel. 8 commits • 8 merged pull requests • 2 contributors since Guard 3.60.0a111. Evidence for this change - cigarMeasure Swarm hand-offs and the Claude Code commit-replay lane (#7948) Evidence for this change
- Merged pull request #7932: fix(daemon-manage): don't count another program's thread as a running daemon
- Merged pull request #7945: feat(swarm): start agents from a command, define their work, and keep them out of folders
- Merged pull request #7930: fix(guard): record why every daemon exit happened
- Merged pull request #7949: fix(cigar): cap advisory prompt workers
- Merged pull request #7944: fix(guard): tell the agent an allowed script changed instead of saying it was never set up
- Merged pull request #7948: bench(cigar): measure Swarm hand-offs and the Claude Code commit-replay lane
- Merged pull request #7941: fix(guard): retire daemons of deleted homes and leftover relays, and sweep abandoned temp files
- Merged pull request #7940: fix(guard): let Watch harness hooks through while the daemon is down, and file Claude Code hooks as Claude Code's
Upgrade and compatibility
None documented.
Compare with the previous release
Predecessor on the same channel: alpha/v3.60.0a111
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.