BACK_TO_COURSEWhat
Installing and Upgrading to v6.2
The Update Procedure, Step by Step
Preview, Apply, Confirm
Update through the template updater. Claude uses .claude/core/; Codex uses .codex/core/ with the same arguments.
node .claude/core/template-updater.js update /path/to/project --merge --dry-run # 1. preview
node .claude/core/template-updater.js update /path/to/project --merge # 2. apply
node .claude/core/render-shared-agents.js --check # 3. confirm projections match
What --merge Keeps
- Your root instructions (managed directives refresh, your prose stays)
- Role personas and Project Context
- Bespoke skills
- Marked project additions
- Local settings
After the Update
- Read the dry-run output before applying — it is the only free look at what will change
- Run the render check; a mismatch means a generated file was edited by hand
- Review or trust newly installed or changed native hooks in your runtime
- Run your application's gate — not the toolkit's test suite
WARNING
Do not force over a conflict to make bytes match. If the updater reports a conflict in a generated file, move your intended change to its canonical source under .agents/, then render. A local canonical edit may also make the next update refuse to overwrite it — that is the safety working, not a bug.
QUIZ
What is the correct order for an update?
Sign in to track lesson progress and earn a certificate.SIGN IN TO SAVE PROGRESS