VigilVerify Your Coding Agent.Claude Code, Cursor, GitHub Copilot and Codex do a lot on your machine. Vigil gives you independent OS-level evidence of what actually happened.
Agent: "I fixed it." Vigil: Here's what the machine observed. Agent: "I didn't access anything unusual." Vigil: Here's the evidence. Agent: "I only changed what was necessary." Vigil: Here's the session record.
What Vigil shows you🔌 MCP activity — every MCP server call your agent makes 🌐 Network connections — outbound connections initiated during the session ⚙️ Process activity — commands and processes spawned by your agent 📄 File activity — files read, written, or deleted 🚨 Red Lines — hard limits you define; Vigil flags anything that crosses them 🔄 Friction signals — unusual patterns worth a second look 🔍 Session evidence — a timestamped record you can query How it worksVigil sits at the OS level, independent of your coding agent. It doesn't rely on what the agent reports — it observes what the machine actually does. The Vigil VS Code sidebar connects to a local backend that monitors file activity, network connections, and process spawns in real time. Claude Code (and other agents) can query Vigil directly via MCP to get a record of their own session activity. Vigil observes. Claude reasons. Developer decides. Works with
Get startedDownload Vigil — installs the local tray app and backend in under two minutes.
Red LinesRed Lines are conditions you define that Vigil should never let pass silently. Examples:
When a Red Line fires, Vigil flags it in the sidebar. You decide what to do next. PrivacyVigil runs entirely on your machine. Nothing is sent to any external server. No telemetry. No cloud dependency. The local backend runs on port 7422 and is only accessible from localhost. You can verify this with any network monitoring tool. Requirements
|
