DevToolsAI SecurityAgentLocal-first

CmdGuard – Local Gate for Agent Commands

A local pre-execution check that approves, flags, or blocks coding-agent commands

Problem
Developers letting coding agents run terminal commands are flying blind—a destructive rm -rf or privilege escalation can wipe out hours of work. Existing safeguards either rely on cloud review or require heavy sandbox setup, leaving a gap for a lightweight, purely local gatekeeper at the command level.
Solution
A local interception layer: before any agent tool call executes, it uses a small local model plus rules to judge risk and output approve, send-for-review, or block. Users can customize allowlists and sensitive-path rules, and all judgment runs offline—no code or commands leave the machine.
Users
Professional developers and small teams using Claude Code, Codex, Cursor, and similar coding agents
MVP
Intercept agent tool calls via a CLI wrapper; built-in rules for common dangerous commands (rm -rf, chmod 777, curl | sh, etc.); local small model for semantic risk classification; pop-up confirm/edit/reject dialog for uncertain calls; simple user-configurable allowlist file.
Revenue
Open-core with paid Pro (team rule sharing, audit logs, Slack alerts); or a $29 one-time license unlocking enterprise rule packs and priority support.
Why now
Coding agents are exploding in popularity, yet command execution security is largely ignored. Local small models (3B-class) now run fast enough on laptops for low-latency risk classification, enabling privacy-safe protection without cloud services.

Source discussions · 1

  1. Hacker NewsShow HN: Laya guard – a local check before your coding agent runs a command2↑ 0
← Back to list