Claude Config Editor CLI
A local web editor for Claude Code config: shows project sizes, deletes old chat histories and manages MCP servers
- 265 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The editor reads and overwrites the whole `.claude.json`, which holds project conversations and MCP server settings
- Deleting a project erases its chat history, and rollback is possible only from `.claude.backup.json`
Install
- Works in
Manual install
git clone https://github.com/gagarinyury/claude-config-editor.git && cd claude-config-editor && python3 server.pyThe editor opens at http://localhost:8765. It needs Python 3.7 or newer and no other packages.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The editor reads and overwrites the whole `.claude.json`, which holds project conversations and MCP server settings
- Deleting a project erases its chat history, and rollback is possible only from `.claude.backup.json`
This is third-party code. Review the repository files before installing.
What it does
Claude Config Editor is a single Python script with a web interface. The `python3 server.py` command starts a local server on port 8765, and the editor finds Claude Code (`~/.claude.json`) and Claude Desktop (`claude_desktop_config.json`) configs on macOS, Linux and Windows by itself. There are no dependencies: the standard library of Python 3.7 or newer is enough. The overview tab shows file size and a list of projects sorted by weight. Claude Code keeps the chat history of every project in one JSON, so after a few weeks the file grows. The editor lets you select the heaviest projects with the Top 10 Largest button, delete their history in bulk and export any project to a separate JSON first. Search and sorting by size, name and message count are included. The MCP Servers tab lists servers with command, arguments, environment variables and working directory. You add and remove a server with buttons instead of hand-editing JSON. Changes stay in memory until you press Save. Before every write the editor copies the file to `.claude.backup.json`, and Claude must be restarted for changes to apply. The author stresses the tool runs locally only, with no network requests or telemetry.
Who it is for. For people who have used Claude Code for a long time, noticed `.claude.json` has swollen to tens of megabytes and want to clean it and their MCP servers without hand-editing JSON.
Good fit when
- The `.claude.json` file has grown very large and Claude Code starts slowly
- You want to delete chat histories of old projects after saving the important ones to JSON
- You want one list of all Claude Code and Claude Desktop MCP servers with commands and environment variables
- You need to add or remove an MCP server quickly without JSON typos
- You want an automatic copy of the configuration in `.claude.backup.json` before cleaning
Not a fit when
- You need the full conversation history of projects and exporting each one by hand is inconvenient
- Claude Code is running and writing to the same file: close it before editing
- You need a package manager install or a CLI command: the project runs as a script from a cloned repository
- A team or deployment system manages the config and manual edits on the machine will be overwritten
Example request
Clone claude-config-editor, run `python3 server.py` and open http://localhost:8765 so I can see the heaviest projects in `.claude.json`.Limitations
- Deleting a project erases its chat history for good once saved. You can roll back only with the `.claude.backup.json` copy the editor makes before writing, or by reloading the page before pressing Save.
- It needs Python 3.7 or newer and starts from a cloned repository with `python3 server.py`.
- The editor changes only the Claude Code and Claude Desktop config files it detects automatically. It does not touch other places where history may be stored.
- Changes take effect after Claude restarts.
- The latest repository changes date from autumn 2025, so check compatibility with newer Claude Code versions on a copy of the file before cleaning.
How to disable. Stop the server with Ctrl+C in the terminal running `python3 server.py` and delete the repository folder. To restore the earlier state copy `.claude.backup.json` back over `.claude.json`.
FAQ
Why is .claude.json so large?
Claude Code stores the chat history of every project in one JSON. The editor lists projects by descending size, and the heaviest can be selected with the Top 10 Largest button.
How do I keep chat history before deleting?
In Project History press Export for the project and the browser downloads a JSON with its conversation. After that you can delete the project and save the changes.
How do I restore the config after a mistake?
Before every save the editor makes a `.claude.backup.json` copy. Put it back over `.claude.json`, and before pressing Save you can discard changes by reloading the page.
Does the editor send data to the internet?
According to the author it does not: the server listens on localhost:8765 with no telemetry or network requests. The code is about three hundred lines of Python and can be read in minutes.
How do I manage Claude MCP servers with this editor?
Open the MCP Servers tab: it shows command, arguments, environment variables and working directory of each server. The add button creates an entry from a name and command, Delete removes it, and after Save Claude needs a restart.
Discussion
No questions or reviews yet.
Related
CLI toolscc-lens
Claude Code Lens (cc-lens)
Local Claude Code analytics: a dashboard of sessions, tokens, cost and projects from your ~/.claude data, no cloud
An MCP server that lets an agent work on your computer: terminal and long-running processes, file search and edits, Excel, PDF and DOCX
A Claude Code plugin: a status line with context, 5-hour and 7-day limits, cost and usage of Codex, Gemini and z.ai
Claude Code History Viewer
claude-code-history-viewer
A desktop app for browsing, searching and analyzing conversation history from Claude Code, Codex CLI, Gemini CLI, Cursor, Cline, Aider and other agents
Minutes
minutes
A local-first MCP server for meeting memory: on-device recording and transcription into Markdown, searchable from Claude Code, Codex, Cursor and any MCP client
A Claude Code plugin that keeps memory across sessions in one local file, with no database, cloud or API keys
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| Claude Config Editor (this entry) | no | 265 | |
| cc-lens | no | 599 | shows analytics of sessions, tokens and cost, while here the config file itself is edited |
| Claude Usage | no | 2,282 | a read-only local dashboard from Claude Code logs, with no config editing |
README in short
The page describes the problem of a bloated `.claude.json`, shows screenshots of three tabs and gives a three-command start. It continues with usage scenarios, a table of config paths per system and answers to common safety questions.