Skip to main content

Requirements

Install via pip

Verify the installation:
Keep your global Python environment clean by using a virtual environment:

Install from source

For the latest unreleased changes:

Configuration

API key setup

Your API key is generated the first time you sign in at zenveil.dev and emailed to you immediately. It starts with zv_live_ and is shown once — store it somewhere safe before closing the email. Set it as an environment variable:
To make it permanent, add it to your shell profile:
Or use zenveil login to authenticate interactively — this stores your key in ~/.zenveil/credentials so you never have to export it manually.
Lost your key? Go to Dashboard → Settings → API Key → Rotate Key. A new key is generated immediately and emailed to you. Your old key stops working the moment you rotate. Update any CI/CD pipelines or .env files that reference the old key.

Optional: AI analysis keys

AI-powered commands (explain, fix, triage, agent) use Claude. Set your Anthropic API key:
Get your key at console.anthropic.com.

Optional: GitHub token

GitHub scanning and auto-PR require a GitHub token with repo scope:
Create a token at github.com/settings/tokens. Required scopes:
  • repo — for private repository scanning and opening pull requests
  • public_repo — for public repository scanning only

Full environment setup

Platform-specific notes

ZenVeil works with the system Python 3 or any Homebrew/pyenv Python.
If you see a command not found: zenveil error, ensure ~/.local/bin is on your $PATH:
If installing globally in CI:
ZenVeil runs natively in WSL2 (Windows Subsystem for Linux). Follow the Linux instructions inside your WSL2 shell.Native Windows support via PowerShell is experimental. WSL2 is the recommended path.
Run ZenVeil in a container without any local Python installation:

Upgrading

Check the current version:

Uninstalling

ZenVeil stores scan caches in .zenveil-last-scan.json (in your project directory) and credentials in ~/.zenveil/. Remove them manually if needed:

Troubleshooting

The pip scripts directory is not on your $PATH.
The anthropic package is not installed in the active environment.
If your company uses a custom CA bundle:
Never use sudo pip. Instead, install to user scope:
Or use a virtual environment (recommended).