Web-based tool for managing Claude Code projects, subagents, slash commands, hooks, and MCP servers
npm install claude-code-config-managerA web-based interface for viewing and managing Claude Code projects, subagents, slash commands, skills, hooks, and MCP servers across your local machine.
Claude Code Config Manager provides a centralized dashboard to browse all your Claude Code configurations from one place. View your project structures, explore subagent definitions, review slash commands, inspect hooks, and examine MCP server configurations—all from a clean, intuitive web interface.
Configuration Viewing:
- Project Discovery - Automatically discovers all Claude Code projects from ~/.claude.json
- Subagent Viewing - Browse and view all project and user-level subagents with full frontmatter specs
- Slash Command Viewing - View all custom slash commands across projects
- Skills Viewing - Browse and view skills (directory-based configurations with SKILL.md and supporting files)
- Hooks Viewing - Display configured hooks from settings files
- MCP Server Viewing - View MCP server configurations
- Search & Filter - Quickly find specific configurations
- Detail Sidebar - View full content with markdown rendering, syntax highlighting, and file tree for skills
Configuration Management:
- Copy Configuration - Copy agents, commands, skills, hooks, and MCP servers between projects
- Delete Configuration - Delete agents, commands, skills, and hooks from projects or user-level
- Conflict Resolution - Smart conflict detection with skip/overwrite/rename strategies
- Single-Click Copy - Streamlined UX for quick configuration duplication
- Cross-Scope Copy - Copy between user-level and project-level configurations
- Smart Merging - Intelligent merge for hooks and MCP configurations
- External Reference Detection - Warns when skills reference files outside their directory
docs/testing/test-reports/- Node.js 18.0.0 or higher
- npm (comes with Node.js)
- Claude Code installed with at least one project configured in ~/.claude.json
``bashInstall from npm
npm install -g claude-code-manager
Usage
$3
For development with Hot Module Replacement (HMR) and instant feedback:
Terminal 1 - Frontend (Vite dev server):
`bash
npm run dev
`
Opens http://localhost:5173 with HMR enabled (< 1s reload on file changes)Terminal 2 - Backend (Express server):
`bash
npm run dev:backend
`
Runs on http://localhost:8420 (API endpoints)$3
Build and serve the optimized production bundle:
`bash
npm run build # Build frontend to dist/
npm start # Start backend server (serves frontend from dist/)
`
Opens http://localhost:8420Deployment
Claude Code Config Manager supports environment-based API URL configuration for different deployment scenarios.
$3
No configuration needed - works out of the box:
`bash
npm run dev
Frontend: http://localhost:5173
Backend: http://localhost:8420 (automatic)
`$3
Configure the backend URL for Docker Compose deployment:
`bash
Copy environment template
cp env.docker.sample .envEdit .env to match your Docker Compose service name
VITE_API_BASE_URL=http://backend:8420
Build and deploy
npm run build
docker-compose up
`$3
Configure the backend service URL for Kubernetes:
`bash
Copy environment template
cp env.kubernetes.sample .envEdit .env to match your Kubernetes service
VITE_API_BASE_URL=http://manager-api.default.svc.cluster.local:8420
Build and deploy
npm run build
kubectl apply -f k8s/
`$3
Override the API URL at build time:
`bash
Set environment variable for custom backend URL
VITE_API_BASE_URL=https://api.example.com npm run build
`$3
VITE_API_BASE_URL - Override the default API base URL
Priority order:
1.
VITE_API_BASE_URL environment variable (if set)
2. Development mode: http://localhost:8420 (Vite dev server on port 5173)
3. Production mode: same origin as frontend (default for most deployments)See
.env.sample for configuration examples.$3
The application will automatically:
1. Read your Claude Code projects from
~/.claude.json
2. Display all discovered projects in the dashboard
3. Allow you to view agents, commands, hooks, and MCP servers for each project$3
- Dashboard - View all discovered projects
- Project Detail - Click any project to see its configurations
- User Configs - Click the purple "User" card to view global configurations
- Detail Sidebar - Click any item to view its full content
- Search - Use the search bar to filter configurations
- Theme Toggle - Switch between dark and light modes
- Rescan - Click the refresh button to reload project list
How It Works
Claude Code Config Manager reads your Claude Code configurations directly from the file system:
$3
- .claude/agents/*.md - Subagent definitions
- .claude/commands/*/.md - Slash commands
- .claude/skills/*/SKILL.md - Skills (directory-based configurations with SKILL.md and supporting files)
- .claude/settings.json - Project settings and hooks
- .mcp.json - MCP server configurations$3
- ~/.claude/agents/*.md - User subagents
- ~/.claude/commands/*/.md - User commands
- ~/.claude/skills/*/SKILL.md - User skills
- ~/.claude/settings.json - User settings, hooks, and MCP servers
- ~/.claude.json - Project registryPlatform Support
Claude Code Config Manager works on:
- Linux
- macOS
- Windows (both WSL and native)
Roadmap
Current Release: v2.3.0 - Agent Skills Support ✅
- PrimeVue Aura theme components throughout application
- Tailwind CSS v4 integration with responsive utilities
- 63% reduction in custom CSS code
- Enhanced accessibility and performance
- See
CHANGELOG.md for complete release notesFuture Enhancements (Planned)
- MCP Server Management - Enable/disable MCP servers directly from the UI
- Team Builder - Create groups of agents, commands, and configurations to copy as a unit
- Subagent CRUD - Create, edit, and delete subagent definitions with YAML validation
- Command Management - Create, edit, and delete slash commands with testing
- Hooks Configuration - Visual editor for configuring hooks with templates
- Advanced Features - Real-time file watching, version history, bulk operations
See
docs/guides/ROADMAP.md for detailed planning.License
MIT License
Support
For issues, questions, or feature requests, please create an issue in the repository.
Development History
This project has undergone continuous improvement with rigorous workflow practices:
Session Summaries:
- October 24, 2025 - Fixed 4 critical display bugs with 100% test coverage
Workflow Analyses:
- October 7, 2025 - Critical incident analysis leading to workflow improvements
- October 12, 2025 - Exemplary execution (5/5 stars)
- October 22, 2025 - Best-practice bug sprint (5/5 stars)
Complete Archive: See docs/sessions/INDEX.md for lessons learned and best practices.
Troubleshooting
$3
- Ensure Node.js 18+ is installed: node --version
- Check if port 8420 is already in use
- Reinstall dependencies: npm install$3
- Verify ~/.claude.json exists and contains project paths
- Try clicking the "Rescan" button in the UI
- Check browser console for errors (F12)$3
- Verify project directories exist and are accessible
- Ensure .claude/` directories have proper read permissions