Update the Knowledge Base
Refresh the installed Knowledge Base and skills to the current release without losing your adoption files, and know which of the three update commands you need.
Goal: bring .pair/ and the skills to the current release; your adoption files stay as they are.
Prerequisites
- A pair-enabled project with a clean git tree
pair-cliat the target version (pair-cli --version)
Which update?
| You want to update | Run |
|---|---|
| the CLI itself | npm update -g @foomakers/pair-cli (or pnpm update -g) |
| the Knowledge Base and skills in a project | pair-cli update |
| the Claude Code plugin (optional path only) | /plugin update pair@pair in Claude Code |
A new pair release usually needs the first two, in that order. The plugin only ships /pair-assistant; updating it never touches .pair/.
Steps
- Update the CLI
- With pair-cli:
npm update -g @foomakers/pair-cli, thenpair-cli --version.
- With pair-cli:
- Update the project
- With pair-cli:
pair-cli update. Add--skip-registries agentsto keep your ownAGENTS.md/CLAUDE.md; a choice saved inpair.config.jsonis honoured without the flag. - With
/pair-assistant(optional, Claude Code): "update pair".
- With pair-cli:
- Follow the migration page, if the release has one
- In your assistant: open Migrations and run the prompts for your version jump step by step.
- Repair links
- With pair-cli:
pair-cli update-link --dry-run, then without the flag (reference).
- With pair-cli:
Verify
pair-cli kb-validatepasses.pair-cli update-link --dry-runreports no broken links.git diff .pair/adoption/is empty: nothing of yours changed.