mcpware/claude-code-organizer

Formerly Claude Code Organizer — a local control panel for AI coding harnesses.
> **AI agents: read AI_INDEX.md first.** It is the navigation manifest for this codebase — where to find every module, how they connect, and where to look before making any claim about the code.
English | 简体中文 | 繁體中文 | 廣東話 | 日本語 | 한국어 | Español | Bahasa Indonesia | Italiano | Português | Türkçe | Tiếng Việt | ไทย
> **New: Activation Scanner research preview.** CCO is adding a paper-backed local activation probe for MCP, skill, plugin, hook, and tool-description poisoning. Source-verified scanner paths we inspected rely on text, rules, or classifiers; this preview adds a different signal by freezing a small local sensor model, reading its hidden activations, and training a probe before an untrusted capability runs. See research/README.md, research/SCANNER_PIPELINE.md, and research/LIVING_PLAN.md.
**Cross-Code Organizer (CCO)** is a cross-harness config organizer for AI coding tools. One dashboard for Claude Code, Codex CLI, OpenCode, DeepSeek Harness (DSH), and future adapters. Switch harnesses from the sidebar, inspect what each tool loads, edit Markdown customizations in place, and clean up your AI coding environment without spelunking through hidden folders.
CCO gives you cross-harness visibility. Claude Code has memories, skills, agents, hooks, slash commands, MCP servers, sessions, and context budget tracking. Codex CLI has AGENTS instructions, custom agents, profiles, sessions, history, shell snapshots, local memory artifacts, TOML config, MCP servers, plugins, hooks, and skills. OpenCode has layered JSON/JSONC config, AGENTS instructions, agents, commands, compatibility skill roots, MCP servers, plugins, tools, and themes. DSH has profiles, layered entry files, global settings, and project/user skill roots. CCO normalizes each harness through its own adapter, without pretending that every harness has the same precedence or mutation rules.
**Rename note for search:** Cross-Code Organizer is the current name of the project formerly known as **Claude Code Organizer** (claude-code-organizer). If you are looking for a Claude Code memory manager, Claude Code MCP security scanner, Codex CLI config viewer, Cross Code Organizer, or cross-code-organizer, you are in the right place.
> **v0.19.3** — Claude Code previews now survive markdown renderer failures, plugin-provided skills are scanned, and project discovery handles non-ASCII paths, lossy encoded paths, and symlinked directories.
> **v0.20.0** — Adds Harness Doctor with an Effective Context Map, explainable hygiene score, reversible exact-duplicate repair, copy-only skill migration, and optional anonymous monthly metrics. Also adds OpenCode and DeepSeek Harness inventory, an All Memories view with body search, full Markdown editing, a resumable Session Distiller repair, local-server hardening, and dependency security updates.
> Scan for poisoned MCP servers. Reclaim wasted context tokens. Disable MCP servers per-project. Find and delete duplicate memories. Move misplaced configs where they belong.
> **Privacy:** CCO reads selected harness config files on your machine (~/.claude/, ~/.codex/, and project-level config). Anonymous metrics require explicit opt-in. When enabled, detailed event totals stay local under ~/.cco/; CCO submits a deduplicated monthly signal containing only a rotating anonymous ID, UTC month, app version, and harness ID. It never sends paths, names, prompts, file contents, sessions, or credentials. See PRIVACY.md.
Explicit opt-in telemetry | No config or content upload | Demo recorded by AI using Pagecast
> 100+ stars in 5 days. Built by a CS dropout who found 140 invisible config files controlling AI coding tools and decided no one should have to cat each one. First open source project — thank you to everyone who starred, tested, and reported issues.
The Loop: Scan, Find, Fix
Every time you use an AI coding harness, three things happen silently:
1. **You don't know what your harness actually loads.** Each tool has its own rules — MCP servers follow precedence, agents shadow each other by name, settings merge across files, AGENTS instructions apply by directory. You can't see what's active without digging through multiple hidden directories.
2. **Your context window fills up.** Duplicates, stale instructions, MCP tool schemas, and inherited project files can load before you type a single word. The fuller the context, the less room your coding agent has for the actual task.