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