Claude Control

Claude Control

**Every Claude Code setting in one place.**

A local web panel for [Claude Code](https://claude.com/claude-code): it reads and edits the real files on disk — `CLAUDE.md`, `settings.json`, skills, hooks, MCP servers — through a UI instead of by hand in JSON and Markdown. Plus a sandbox, where a change is tested before it becomes your daily setup.

Runs entirely on your machine: no account, no server, no telemetry.

By default the panel configures Claude Code, where everything is available; it also edits the configuration of Codex, Gemini, Qwen Code, Continue, Goose, Kimi Code, Cursor, OpenCode and Aider — each in its native format, see [CLIs other than Claude](#clis-other-than-claude).

🇷🇺 [Русская версия](README.ru.md) · 🔧 [Setup](docs/SETUP.md) · 🛠 [Troubleshooting](docs/TROUBLESHOOTING.md) · 🏗 [How it works](docs/ARCHITECTURE.md) · 🔒 [Security](docs/SECURITY.md) · 📱 [Access from a phone](docs/REMOTE.md) · 💬 [Chat and parallel agents](docs/CHAT.md) · 👥 [Groups](docs/GROUPS.md) · 🧑‍💻 [Development](docs/DEVELOPMENT.md) · 🚫 [What the panel does not do](docs/LIMITATIONS.md)

[!TIP] **Won't start?** `pnpm doctor` explains every finding. Still stuck — open Claude Code in this folder and say "it won't start, figure it out": it reads [CLAUDE.md](CLAUDE.md), the map of this project written for the agent, and starts with diagnostics rather than with the code.

---

Why

Claude Code's configuration is plain files, which is a good decision while there are few of them. Then comes a thousand-line `CLAUDE.md`, dozens of skill folders, hooks three levels deep in `settings.json`, MCP servers in a different file altogether, permissions nobody remembers adding. Three simple questions get hard: **what is actually active right now, what does this hook fire on, what breaks if I add this rule.**

The panel answers them: a visible shape, a switch that deletes nothing, and a sandbox where a change is tested against real Claude Code before it becomes