AgentGuard is a local desktop application that serves AI coding agents (such as Claude Code, Codex, etc.). Its core positioning is to change the agent's behavior before a request is sent, reducing sensitive information leakage and token waste. It contains two main functional modules: Guardian Agent and Token Saver.
-
Guardian Agent Guardian performs checks before a request is submitted to the model. Its main capabilities include: implementing DLP (data loss prevention) on prompts, tool inputs, and file reads, intercepting sensitive content such as keys; setting token limits on overly large requests; providing vulnerability protection when installing dependencies or writing dependencies; and offering update suggestions for outdated version pins. The official website describes it as covering all integration paths and giving allow-or-deny decisions at stages such as prompts, tool inputs, and dependency installation.
-
Token Saver Token Saver is responsible for trimming redundant content before the context reaches the model. Its main capabilities include: compressing verbose shell output; caching repeated file reads; streamlining noisy responses such as searches, diffs, and JSON; and tracking the number of tokens saved in logs and analytics. The official website states that Token Saver currently has the deepest coverage on Claude Code.
-
Usage and Viewing Interfaces According to the official website, the overall flow is: a request comes in, Guardian or Token Saver performs processing, and then multiple viewing interfaces keep traceable records. The viewing interfaces include: Logs, Analytics, and Garden. Logs provides a compact event history, recording Guardian's decisions and Token Saver's reductions, and supports exporting traces; Analytics provides charts showing total tokens and savings, latency, and tool call trends, helping determine whether the tools are actually working; Garden turns project activity into a visual map, using grove to represent modules and tree to represent files, and displaying symbols and import relationships.
-
Integration Methods The official website mentions that there are three integration methods in total, with different depths of coverage: one provides the most complete coverage, including Garden's file and symbol signals; one focuses on Guardian, performing DLP and token limit checks, dependency installation protection, and Garden pathinferred from bash tool usage; the other is hook-based outbound control, giving Guardian-style allow-or-deny decisions and providing dependency suggestions in supported interfaces, while also capturing project activity for Garden and logs.
-
Build and Platform The official website does not list specific supported operating systems. If your operating system version is not found, the official recommendation is to clone the code repository and build it yourself using npm install && npm run tauri build. Apart from this, the official website currently does not provide information such as pricing, charging model, or detailed installation steps.
