Repository navigation
v1.4.0
馃殌 CPMM v1.4.0 (Minor)
A Context7-focused release that aligns CPMM with the official Context7 Claude Code flow, removes conflicting repo-local Context7 behavior, and makes setup, verification, and current-doc lookup much clearer for users who opt in.
What Changed
CPMM now follows the official Context7 path:
- CPMM no longer ships a parallel repo-local Context7 docs layer.
cpmm setupcan now offer the full recommended official flow:npm install -g ctx7ctx7 setup --cli --claude
- This gives users both:
- a shell-visible
ctx7CLI - the official Context7 Claude Code integration
- a shell-visible
Context7 verification is now clearer:
cpmm doctornow checks Context7 in two parts:ctx7CLI binary presence- official Claude integration artifacts
- It reports:
ctx7binary- Context7 skill (
find-docs) - Context7 rule (
context7.md)
- Partial installs now get explicit recovery guidance instead of ambiguous status:
- re-run
cpmm setup - or run the official commands directly
- re-run
Legacy Context7 cleanup improved:
- If CPMM detects the old managed Context7 MCP entry in
~/.claude.json, setup now removes it. - This prevents old repo-managed Context7 configuration from conflicting with the new official path.
Current-doc behavior is cleaner:
- After official setup, current library docs flow through Context7鈥檚 official Claude integration.
/llms-txtremains available as the explicit raw-doc fallback when you want raw/llms.txtcontent or URL-based raw-doc lookup.
Documentation and built-in CPMM guidance were updated (EN/KO):
README.mdREADME.ko.mddocs/USER-MANUAL.mddocs/USER-MANUAL.ko.md
Claude command / skill guidance was also updated to reflect:
- official Context7 ownership
- the new verification model
/llms-txtas the explicit fallback path
Why This Matters
Users now get a much cleaner Context7 experience:
- no more mismatch where official setup succeeds but
ctx7is missing from the shell - no more split mental model between CPMM-managed docs behavior and official Context7 behavior
cpmm setup,cpmm doctor, shell verification, and Claude-side behavior now point to the same installation model
CPMM keeps its original product boundary intact:
- Context7 remains optional
- CPMM does not make Context7 a default dependency
- users who do not opt into Context7 keep the same default CPMM behavior
Upgrade
npm i -g claude-pro-minmax@latest
cpmm setup
cpmm doctorOptional Context7 Enablement
npm install -g ctx7
ctx7 setup --cli --claude
cpmm doctorRecommended Verification
command -v ctx7
ctx7 --version
cpmm doctorCompatibility Note
Users upgrading from v1.3.1 without Context7 enabled:
- default CPMM behavior remains unchanged
Users enabling Context7 on v1.4.0:
cpmm setupnow installs thectx7CLI and then runs the official Claude Code setupcpmm doctornow verifies both the CLI and the official integration separately- current-doc lookup now follows the official Context7 path, with
/llms-txtkept as the explicit raw fallback