Vanzik 2.0.0 — Release Notes

Released: 2026-10-26 Headline: AgentGuard is now Vanzik. Same guard, new name, and upgrading moves your install for you.

Check these before you upgrade. - Every name that said AgentGuard says Vanzik, with no alias for the old one: programs, VANZIK_* environment variables, folders, login services, headers, metrics and packages. - An AGENTGUARD_* variable that would be used now stops the program instead of being ignored, so a server never runs without the API key its operator configured. - 1.x's in-place update (agentguard setup → Update) can't install 2.0; use the 2.0 installer. See MIGRATION.md § v1.x to v2.0 (github.com).

Why this release exists

2.0 renames the project, and the rename, including refusing the old AGENTGUARD_* variable names, is its only breaking change. Everything else is an addition (vanzik migrate --from-agentguard, the server adopting an agentguard.db) or a fix. The policy schema, the /v1/* wire protocol, the audit log format and seal, the store and every command's existing flags are as in 1.4.0, so policies, audit logs and databases carry over unchanged.

A rename is risky in one place: the coding-agent hooks AgentGuard connected run the agentguard program, and most agents let a tool call through when a hook's program is missing. So 2.0 doesn't leave the move to you.

What's new

Upgrading moves an existing install: vanzik migrate --from-agentguard

The 2.0 installers run it after installing, and vanzik setup runs it before its menu. It:

• stops and removes AgentGuard's login service first, and changes nothing if it can't;
• moves the config and data folders by renaming them, so the policy, API key, audit log and seal key keep their bytes;
• renames agentguard.db to vanzik.db and updates setup.json's paths;
• points the Claude Code, Cursor, Gemini CLI and Codex hooks AgentGuard wrote at vanzik, keeping --fail-closed, your own hooks, and a .vanzik-backup of every file it edits;
• installs the login service again under the new name and waits for the server;
• lists what is left to do by hand: trusting the changed hook in Codex, AGENTGUARD_* variables, MCP client configs that start the old gateway, the old programs.

vanzik server also renames an agentguard.db it finds in its --data-dir instead of starting on an empty database.

Breaking changes

Folders, login services, headers (X-Vanzik-*), metrics (vanzik_*), cookies and the rest are in the full table in MIGRATION.md (github.com).

Other fixes

• Agent settings files saved with a UTF-8 byte order mark (as Notepad does) can be connected, disconnected and migrated; they were refused as invalid JSON.

Get started

:::bash
curl -fsSL https://github.com/lictorate/vanzik/releases/latest/download/install.sh | sh
vanzik setup

# or
docker run -d -p 8080:8080 -e VANZIK_API_KEY="$KEY" \
  -v vanzik-audit:/var/lib/vanzik ghcr.io/lictorate/vanzik:2.0.0

go install lictorate.com/vanzik/v2/cmd/vanzik@v2.0.0
pip install "vanzik==2.0.0"
npm install @lictorate/vanzik@2.0.0

Releases before 2.0 stay on PyPI as agentguardproxy and on npm as @lictorate/agentguard.

Full change list: CHANGELOG.md § 2.0.0 (github.com).