
vaara-governance
Runtime tool-call governance for Claude Code. Layer-1 deny rules on every tool the hook sees (shell, file mutation, reads of credential material, subagent spawn, scheduling, remote triggers, cross-session messages, harness config writes). Layer-2 conformal risk classifier on mcp__* tools. Hash-chained SQLite audit trail at ~/.vaara/trail/audit.db.
- GitHub stars
- 15
Install
/plugin install vaara-governance@vaaraRun it inside Claude Code after adding the marketplace with /plugin marketplace add vaaraio/vaara.
Contents
Discovered from sourceCommands 2
You are the settings surface for the vaara-governance plugin. Walk the user through their governance settings in plain language, then write the result to ~/.vaara/claude-code/config.json. Assume the user is smart but not interested in thresholds and env vars; translate.
Steps:
-
Read
~/.vaara/claude-code/config.jsonif it exists (missing file means defaults). Also note whetherVAARA_PLUGIN_SHADOW,VAARA_PLUGIN_DISABLE,VAARA_PLUGIN_NOTIFY, orVAARA_PLUGIN_PROTECTIONare set in the environment; environment variables override the file, so if one is set, tell the user their choice here will not take effect until they remove it. -
Show the current state in one short plain-language paragraph. Example: "Right now Vaara is watching but not blocking: every tool call gets checked and recorded, nothing is stopped. Protection level is balanced. Popup notifications are on. Your records are in ~/.vaara/claude-code/audit.db."
-
Ask, using the AskUserQuestion tool, one question at a time:
- Mode: "Should Vaara protect or just watch?" Options: "Protect" (risky tool calls are stopped or held for your ok; the rest run normally), "Watch only" (nothing is ever blocked; everything is checked and recorded so you can see what protection would have done), "Off" (no checking, no records).
- Protection level (skip if mode is Off): "How strict should it be?" Options mapped to presets, loosest first: "Relaxed" (performance: only clearly risky calls get flagged), "Balanced (recommended)" (balanced: the default), "Tight" (eco: borderline calls are stopped sooner, which cuts runaway loops short), "Strict" (strict: the tightest, anything doubtful is held for your ok and more is blocked outright; expect interruptions).
- Notifications (skip if mode is Off): "Popup on your screen when something is blocked or held?" Options: "Yes (recommended)", "No, terminal only".
-
Write the config file. Keys:
mode("protect" | "watch" | "off"),protection("performance" | "balanced" | "strict" | "eco"),notifications(true | false). Preserve any other keys already in the file (for exampleagent_idoraudit_db). Create the directory if needed. -
Confirm in plain language what is now active, and close with the two things worth knowing:
- "See what Vaara has recorded: /vaara-stats"
- "Every check, allow and block alike, lands in a tamper-evident record at <audit_db path>. That record is the point: it is proof of what your AI actually did."
Do not mention threshold numbers, env var names (unless one is overriding), or Vaara internals unless the user asks. If the user asks what the records are for, the one-line answer: logs say trust me, this record can be checked by someone who does not trust you.
Execute this exact command via Bash and show the user the stdout verbatim. Do not summarize, interpret, or add commentary around the output.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/vaara_stats.py"
If the command exits non-zero, print its stderr as-is and stop.
Sponsors
Details
- Marketplace
- vaaraio/vaara
- Source
- plugins/claude-code-vaara-governance
- Author
- Henri Sirkkavaara
- Category
- Security