DCG fixes an OpenCode v2 hole that skipped shell checks

A command guard can be installed and still miss an agent’s shell calls. Destructive Command Guard’s v0.16.0 release documents exactly that problem for OpenCode v2, alongside a bridge fix for Oh My Pi and new integrations for Amp, Muse Code and Factory Droid.

The community project’s November 1 release says OpenCode v2 renamed its shell tool from bash to shell. Earlier generated dcg plugins returned early for tool names other than bash, leaving those v2 shell calls unchecked. The updated plugin handles both names and also checks other tools carrying a command argument, according to the release notes.

For existing users, replacing the dcg binary alone is insufficient. The project says to run dcg install --opencode --force or dcg install --omp --force after upgrading, then restart the agent. The fixes live in generated integration files. These are the author’s upgrade instructions; AITrending has not installed or independently tested the release.

The bridge must handle missing answers too

The Oh My Pi integration previously allowed a command when dcg exited with certain codes without a readable allow verdict. The release says empty, malformed or unknown output now follows the configured unverified-decision policy. This closes a different integration gap from recognizing a tool’s name.

Another change makes an unreadable or invalid user or system configuration block shell commands instead of silently falling back to defaults. The release recommends checking a harmless git status command after updating to confirm that configuration loads. An automatically discovered malformed repository configuration has a different, nonfatal treatment.

DCG is a local command-checking tool and set of agent hooks, not a model provider. Its README documents Linux, macOS, WSL and native Windows installation routes, with Codex CLI support starting at 0.125.0. Installing hooks changes the agent’s local execution path and configuration; users still need their existing coding-agent account and model access. The reviewed documentation labels dcg’s license custom.

An upgrade with explicit limits

The project documents remaining false positives, dynamic process calls it cannot fully inspect and hook inputs that can be allowed when oversized under default settings. Its release notes also acknowledge failing tests and deliberate changes that permit some previously blocked heredoc forms.

Those disclosures make this an actionable integration update, not a guarantee that every destructive command will be intercepted. The useful takeaway is to verify the actual host tool, regenerated integration and failure policy, rather than treating the presence of a guard binary as proof of coverage.