Safe Config Explorer Usage

Safe Config Explorer Usage

The Config Explorer provides a consolidated view of Claude Code and Codex configuration. Most surfaces are read-only; supported low-risk text artifacts have carefully gated write paths with backups.

Inspect before changing

Use the explorer to inventory configuration scopes, hooks, MCP servers, skills, plugins, commands, memory files, and provider settings. Identify which layer owns a value—user, project, local, managed, or provider-specific—before editing anything.

Safety model

• Requested paths are canonicalized and restricted to allowed roots.
• Symlinks cannot be used to escape trusted configuration directories.
• Only supported artifact types are writable.
• Write paths create timestamped backups under the relevant cc-config-backups location.
• Broad provider configuration remains inspection-only where safe mutation cannot be guaranteed.

Change procedure

1. Export or copy the current relevant file.
2. Note scope, path, ownership, and permissions.
3. Make one narrowly scoped edit.
4. Review the created backup.
5. Validate provider configuration or start a controlled session.
6. Confirm hooks and MCP still load.
7. Roll back from the timestamped backup if behavior changes unexpectedly.

Avoid these shortcuts

• Do not follow a displayed path outside the allowed roots with shell mutation.
• Do not replace a whole config when changing one supported text artifact.
• Do not remove unknown hooks or MCP entries without identifying their owner.
• Do not expose config dumps in issues; they may contain command paths, endpoints, or secrets.
• Do not enable MCP mutations globally merely for inspection.

Team use

Treat configuration findings as drift evidence. Compare intended policy with observed settings, propose a reviewed change, then apply through the owning repository or management system when one exists. The explorer should not become a shadow configuration manager.

See the exact endpoints and supported surfaces in the API reference.