Dicklesworthstone/destructive_command_guard v0.6.12

on GitHub

Careful company policy for Windows coding agents

This release adds the opt-in careful_company_running_windows preset for
Windows workstations where coding agents may run without interactive command
approval.

The preset supplements dcg's normal destructive-operation protection with
company-oriented guardrails:

• blocks outbound email, chat/webhook sends, HTTP file uploads, remote file
  transfer, public tunnels/raw channels, and attempts to disable endpoint,
  audit, hook, or dcg controls;
• pins the relevant Windows, database, storage, remote, backup, secrets, and
  cloud packs, including Snowflake destructive-query protection;
• applies equivalent outcomes to native PowerShell and cmd.exe, including
  caret escaping, nested cmd /c and call, and common Cmd control-flow
  wrappers;
• keeps ordinary development practical: HTTP reads/downloads, internal
  destinations, package installation, named-remote Git pushes, and direct
  hfdt/hfdt.exe invocations remain available.

This release also closes Windows filesystem gaps around PowerShell/.NET
recursive directory deletion and preserves caller-proven shell dialects so
POSIX rm syntax is not misclassified as a PowerShell alias.

Install on Windows

Download the repository's install.ps1, then run:

powershell -ExecutionPolicy Bypass -File .\install.ps1 -Version v0.6.12 -Verify

Enable the preset in dcg's pack configuration:

[packs]
enabled = ["careful_company_running_windows"]

Validation

• Native x86_64-pc-windows-msvc release build from tag v0.6.12
• 348/348 PowerShell/Cmd E2E scenarios passed on a Windows workstation
• 373/373 Unix E2E scenarios passed
• Full Rust all-target test suite, all-target check, clippy with warnings
  denied, formatting, and Windows cross-compilation passed
• Public PowerShell installer download, mandatory SHA-256 verification,
  extraction, version check, and self-test passed on Windows

The DSR fallback release includes the ZIP's mandatory per-file SHA-256 and a
combined SHA256SUMS. It does not include a GitHub Actions OIDC Sigstore
bundle or a minisign signature; the installer reports that explicitly and
continues only after the mandatory checksum succeeds.