ccx-ecc-mem

# ccx-ecc-mem `ccx-ecc-mem` is a lightweight, bilingual, and Claude Code local capability platform. It integrates memory, retrieval, hook governance, capability orchestration, and Viewer console into a unified product, rather than combining `ccx-mem` and Everything Claude Code as two separate systems. The project adopts a capability-oriented design: core capabilities are registered in `plugin/fusion/registry.json` as capabilities with bilingual metadata, dependency levels, sources, states, and implementation paths. Complete ECC skills/commands/agents/docs/rules are pre-installed as a local capability library; ECC skills are exposed to Claude Code for automatic selection based on descriptions, commands are exposed through curated fusion, and agents, uninternalized ECC hooks, external MCP, and heavy runtimes still require explicit enablement. ## Current Status - Default product surface: local worker, hook lifecycle, memory capture, SQLite lightweight retrieval, Viewer capability center, core skills/commands. - Capability registry: `plugin/fusion/registry.json` - Build-generated capability view: `plugin/fusion/active-view.json` - Viewer capability API: `GET /api/viewer/capabilities` - ECC featured skills/commands: included in default core as internalized capabilities. - ECC complete resources: pre-installed with release package; skills exposed to plugin system for automatic selection; commands exposed through curated fusion; hooks/MCP/runtimes not auto-run. ## Quick Start Install dependencies and build: ```bash npm install npm run build ``` Run tests: ```bash npm test ``` View CLI help: ```bash node dist/npx-cli/index.js --help ``` Check worker status: ```bash npm run worker:status ``` Check npm package contents: ```bash npm pack --dry-run ``` ## Commands - Build: `npm run build` - Full testing: `npm test` - Server-specific testing: `npm run test:server` - Search-specific testing: `npm run test:search` - Context-specific testing: `npm run test:context` - Infrastructure-specific testing: `npm run test:infra` - Worker status: `npm run worker:status` - Worker start: `npm run worker:start` - Worker stop: `npm run worker:stop` - Worker restart: `npm run worker:restart` Avoid running `npm run build-and-sync` in regular development validation, as it synchronizes with the local Claude plugin marketplace and restarts installed workers. ## Architecture Core execution chain: ```text plugin/hooks/hooks.json -> src/cli/hook-command.ts -> src/services/worker-service.ts -> src/services/worker/http/routes/* -> src/ui/viewer/* ``` Key modules: - CLI entry: `src/npx-cli/index.ts` - MCP server: `src/servers/mcp-server.ts` - Hook command: `src/cli/hook-command.ts` - Worker service: `src/services/worker-service.ts` - Worker HTTP routes: `src/services/worker/http/routes/` - Viewer UI: `src/ui/viewer/` built to `plugin/ui/` - Plugin manifest: `plugin/.claude-plugin/plugin.json` - Plugin hooks: `plugin/hooks/hooks.json` - Native skills: `plugin/skills/` - Capability registry: `plugin/fusion/registry.json` - Capability active view: `plugin/fusion/active-view.json` ## Capability Boundary - `plugin/fusion/registry.json` is the sole source of truth for user-visible capabilities. - `scripts/build-hooks.js` generates `plugin/fusion/active-view.json` from the registry. - `src/npx-cli/commands/install.ts` records capability profile, locale, and enables core and optional capabilities during installation. - `src/services/worker/http/routes/ViewerRoutes.ts` exposes capability view through `/api/viewer/capabilities`. - `src/ui/viewer/components/CapabilityCenter.tsx` displays the capability center in Viewer. - Default core capabilities must maintain minimal dependencies and should not introduce external service credentials, uninternalized ECC hooks, Playwright, PM2, ccg-workflow, or heavy language toolchains. - Complete ECC skills/commands/agents/docs/rules are pre-installed; ECC skills are automatically discoverable, ECC commands are exposed only through curated fusion, and ECC agents are enabled only in explicit profiles. - Uninternalized ECC hooks, external MCP catalog, media generation, and heavy runtimes do not automatically connect to the hook/MCP main chain and require explicit configuration or subsequent internalization. ## System Requirements - Node.js 18 or higher - Bun 1.0 or higher - Claude Code with plugin support - SQLite 3 (used at runtime) - Optional dependencies like uv / Chroma MCP for enhanced retrieval ## Language Strategy Bilingual support is provided, with Chinese as the default user language. CLI documentation, Viewer labels, capability titles/summaries, plugin metadata, prompts, and command descriptions should prioritize Chinese and provide English fallbacks. Code identifiers, protocol fields, commands, and paths remain in their original form. ## License and Origin - Runtime code is licensed under AGPL-3.0; see [LICENSE](LICENSE). - Internalized and pre-installed Everything Claude Code resources retain MIT licensing; a copy is included in the release package at `plugin/ecc/LICENSE.everything-claude-code` and `plugin/fusion/LICENSE.everything-claude-code`. - ECC complete resources are pre-installed with the release package, but only skills/commands are exposed as discoverable capabilities; hooks/MCP/runtimes do not auto-run.