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

Agent config file locations

Each agent reads settings from user, project and system scopes, for example ~/.claude/settings.json, ~/.codex/config.toml and ~/.gemini/settings.json. Collecting these files tells you not only that an agent is installed but how it is set up, including approval modes and MCP servers. Treat project scoped files as inventory too, because they travel with repositories.

Read in this order

  1. OfficialClaude Code: Settings files and precedenceStart here: which settings files exist and which one wins.
  2. OfficialCodex configuration referenceEvery Codex config key, including approval and sandbox modes.
  3. OfficialCursor rules (project and user scopes)How project and user rules differ, since project files travel with the repo.

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.