v1.2.4

AgentGuard 1.2.4

• AgentGuard commands and installer results no longer trigger post-tool blocking or redaction. Execution-time approval remains in place.
• Routine events stay local; reportable events send only concise, redacted summaries to Cloud.
• Fixed Cloud reporting for blocked batch findings and recognition of partial installer output.

v1.2.1

Added

• Added opt-in, local-first LLM traffic privacy protection with PII and relay detection, semantic prose analysis, capability-aware enforcement across supported agents, and redacted Cloud synchronization. Enable semantic analysis with agentguard privacy enable; it is off by default and never applies to live prompts.
• Added native Windows scheduled jobs and DSH threat-feed subscriptions, self-checks, and active-session notifications.
• Expanded scanning to support HTTPS GitHub repositories with --ref, plus DSH profile plugin discovery and risk scanning in agentguard checkup.

v1.1.29

Added
Added the read-only DSH installation scanner, native DSH tool plugin, dual full-repository/runtime-surface risk views, review priority, generated-code context, evidence aggregation, and explainable Markdown/HTML/JSON reports.
Added a pinned real-world DSH regression benchmark with deterministic snapshots and manual source-review records for representative LOW-through-CRITICAL artifacts.
Added structured DSH scan coverage accounting and explicit configured runtime-mode visibility in startup logs and runtime summaries.
Changed
MCPB release builds now publish the bundle as agentguard.mcpb so Anthropic's directory auto-pickup keeps matching the asset across version tags.
Relaxed OpenClaw file read/write handling so ordinary paths are allowed by default, while sensitive paths still require approval and critical system mutations still block.
Changed curl/wget | bash/sh handling to require approval by default and block only when hard indicators or multiple suspicious signals are present.
Fixed
Updated compatibility with DSH 0.1.1-rc.2: profile installs now authorize AgentGuard package builds, tarball acceptance uses pnpm's exact local-file build key, and the persistent PowerShell pwsh tool is classified as shell execution for runtime policy evaluation.
DSH protect hooks now exempt only the four exact AgentGuard-owned tool names, preventing third-party agentguard_* tools from bypassing runtime policy evaluation.
DSH runtime scanning now includes referenced generated dist/ and build/ files, while protect mode requires explicit decisions for MCP, skill-install, and unknown tools.
DSH scans now fail closed with DSH_SCAN_INCOMPLETE and expert-review-required when matching files are omitted by the file-count limit, exceed the per-file byte limit, or cannot be read, preventing incomplete scans from returning safe-to-try.

v1.1.28

version patch