ccexp CLI
A terminal explorer for Claude Code configuration: CLAUDE.md, commands, subagents and settings.json with a preview
- 270 ★ on the repository
- Last commit
Extended access
Why this level
- The tool reads configuration files, including `~/.claude/settings.json`, which can hold tokens and hook commands
- Menu actions copy files into the current directory and launch an external editor or the default application
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/ccexpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The tool reads configuration files, including `~/.claude/settings.json`, which can hold tokens and hook commands
- Menu actions copy files into the current directory and launch an external editor or the default application
This is third-party code. Review the repository files before installing.
What it does
ccexp opens a terminal interface and finds Claude Code configuration files in a directory. The file list sits on the left and a preview on the right: `CLAUDE.md` and `CLAUDE.local.md` render as Markdown with syntax highlighting. It sees project and user commands from `.claude/commands/` and `~/.claude/commands/`, subagents from `.claude/agents/` and `settings.json` files with local overrides. You move through the list with the arrow keys, Tab switches panes and `/` jumps to a search that filters files as you type. Enter opens an action menu: copy the content, the absolute or relative path, put a copy of the file in the current directory, or open it in `$EDITOR` or the default application. It runs without installation through `npx ccexp@latest` or `bunx ccexp@latest`, and a global install is only for people who use it all the time. The `--path` flag sets the directory to scan, so you can look at a whole workspace of projects or `~/.claude` at once. The package is written with React Ink and needs Node.js 20 or newer.
Who it is for. Claude Code users whose settings are scattered across projects and the home directory and who need to find and view a file fast.
Good fit when
- In a workspace with dozens of projects you want to see where the `CLAUDE.md` files are and what rules they hold
- You want to compare user commands from `~/.claude/commands/` with project ones and copy one into another repository
- Subagents and settings have piled up and you want to open a specific `settings.json` in your editor fast
- Before cleaning up configuration you want to browse all Claude Code files in a project once
Not a fit when
- You want to edit configuration inside the tool: ccexp only lists files and opens them in an external editor
- You need to manage MCP servers and permissions: it finds the listed files and does not change agent settings
- The settings belong to another agent such as Cursor or Codex: ccexp looks for Claude Code files
- Your environment has no terminal UI: the tool draws in the console and has no graphical version
Example request
Run ccexp for the ~/projects folder and show which projects have a CLAUDE.md and their own slash commandsLimitations
- It needs Node.js 20 or newer and a terminal that supports a React Ink interface.
- It only looks for the Claude Code files listed in the README: memory, commands, subagents and settings.
- `CLAUDE.local.md` is marked deprecated in Anthropic's docs, but ccexp still shows it.
- The old `claude-code-explorer` npm package is the previous version, and the current name is ccexp.
- Menu actions copy and open files, and configurations are not validated for correctness.
How to disable. If you installed it globally, remove the package with `npm uninstall -g ccexp`. A run through `npx` or `bunx` leaves nothing behind except the package manager cache.
FAQ
How do I run ccexp?
Run `npx ccexp@latest` or `bunx ccexp@latest` in the target directory, with nothing to install first. For regular use install the package globally with `npm install -g ccexp`.
Which files does ccexp show?
Memory files `CLAUDE.md` and `CLAUDE.local.md`, commands from `.claude/commands/`, subagents from `.claude/agents/` and `settings.json` files with local variants, both project and user ones.
How do I choose the directory to scan?
Use the `--path` flag, for example `ccexp --path ~/projects` or `ccexp --path ~/.claude`. Without it the tool scans the current directory.
Which keys does the menu have?
Enter opens the menu, where `c` copies content, `p` the absolute path, `r` the relative path, `d` puts a copy in the current directory, `e` opens the editor and `o` the default application.
Does ccexp change Claude Code settings itself?
No. The tool reads and shows files, and you make edits in the editor it opens with the `e` key.
Discussion
No questions or reviews yet.
Related
CLI toolsA debugging tool for Claude Code that reads the session logs already saved on disk and shows exact file paths, diffs, model thinking and a category-by-category
Reads Claude Code session logs as a conversation: tool calls, token counts and a live tail of a running session.
A set of slash commands, skills and subagents for Claude Code: review, tests, security, releases, docs and GitHub to Linear sync
A Claude Code environment installer: CLAUDE.md, rules, skills, agents, hooks and two-layer project memory in one script
A set of 24 slash commands for the Claude Code CLI: commits, review, refactoring, tests and cleanup without repeating the same prompts
A Claude Code working configuration: a planner with per-milestone review, sub-agents and skills for analysis, refactoring and docs sync
Comparison with similar tools
Cards that share the main search query, and how they differ.
README in short
The README presents ccexp as the short name of claude-code-explorer, built on React Ink. It lists features, shows screenshots, names the files the tool finds, and explains running via bunx, npx and pnpm, command-line flags, example scenarios and key bindings.