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

Coding agents on the fleet

Coding agents arrive as CLIs installed through npm or Homebrew, as IDE extensions, as standalone editors like Cursor, and as cloud agents that never touch a laptop. Each keeps its config in a predictable place, which makes those paths the most reliable discovery signal. Keep a per agent list of binaries, extensions and config paths.

Read in this order

  1. OfficialClaude Code: Explore the .claude directoryStart here: a full tour of where one CLI agent keeps its files.
  2. OfficialCodex: Config basicsThe same exercise for Codex, so you can compare two config layouts.
  3. OfficialCursor Enterprise documentationShows what an editor based agent exposes to enterprise administrators.

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.