#configuration
5 articles
-
CLAUDE.md vs AGENTS.md vs GEMINI.md: keep one source of truth across three tools
How Claude Code, Codex and Gemini CLI load their context files, and how to keep one source of truth with imports, context.fileName and symlinks instead of three copies.
-
Pin environment variables in Claude Code's settings.json with the env key: precedence and pitfalls
How the env key in Claude Code's settings.json works: it overrides shell variables, applies to every session and subprocess, and when a saved change reaches a running session.
-
Adding MCP servers to Claude Code: claude mcp add versus .mcp.json
Add and manage MCP servers in Claude Code: claude mcp add for stdio and HTTP servers, the local / project / user scopes, sharing via .mcp.json, authentication and troubleshooting.
-
How to write CLAUDE.md: the three levels (user, project, directory) and a ready-to-use template
Where Claude Code looks for CLAUDE.md, which level wins, what belongs in it and what does not, plus a template you can drop into a small or medium web project today.
-
Switching models, reasoning effort and profiles in Codex CLI's config.toml
The settings you actually touch in ~/.codex/config.toml: model and reasoning effort, task-specific profiles with --profile, and how options, profiles and defaults take precedence.