By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Vendor and version drift

Agent clients ship weekly, and a release can change default permissions, add tools or alter how hooks run. Choose release channels on purpose, set a minimum version through managed settings, and read changelogs for security relevant changes before they reach the fleet. Vendor side changes to models and infrastructure can shift behavior even when nothing changed on your machines.

Read in this order

  1. OfficialAdvanced setup, including release channels and updates (Claude Code docs)Start here: pick a release channel and control how updates roll out.
  2. OfficialClaude Code CHANGELOG (GitHub)A real changelog to practise spotting permission and hook changes in.
  3. ArticleA postmortem of three recent issues (Anthropic)A vendor side change that altered behavior with no client update.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.