How to update your Convoke installation to the latest version.
# Update the package
npm install convoke-agents@latest
# Preview changes (dry run)
npx -p convoke-agents convoke-update --dry-run
# Apply the update
npx -p convoke-agents convoke-updateYour data is backed up automatically before any changes.
Main update command — applies migrations and refreshes your installation.
| Flag | Description |
|---|---|
--dry-run |
Preview changes without applying |
--yes or -y |
Skip confirmation prompt |
--verbose or -v |
Show detailed output |
npx -p convoke-agents convoke-update --dry-run # Preview
npx -p convoke-agents convoke-update # Apply with confirmation
npx -p convoke-agents convoke-update --yes # Apply without confirmationShow current version, latest available version, and migration history.
npx -p convoke-agents convoke-versionRun diagnostics on your installation. Checks project root, config validity, agent files, workflows, output directory permissions, migration lock status, and version consistency — with actionable fix suggestions.
npx -p convoke-agents convoke-doctorWhy
-p convoke-agents? The CLI commands (convoke-update,convoke-doctor, etc.) are binaries inside theconvoke-agentspackage. Without-p convoke-agents, npx tries to find a standalone package with that name, which doesn't exist.
Breaking changes: None
What happens:
- Isla (Discovery & Empathy Expert) and Max (Learning & Decision Expert) agents added
- 6 new workflows installed (empathy-map resurrected for Isla)
- Installer updated to
convoke-install-vortex - Legacy installers (
install-emma,install-wade) show deprecation warnings
Breaking changes: None
What happens:
- Architecture refactor (internal — no user-facing changes)
- Agent files and workflows refreshed
- Isla + Max agents added with 6 new workflows
Breaking changes:
- Workflow renamed:
empathy-map→lean-persona(for Emma) - Agent roles updated:
empathy-mapper→contextualization-expert,wireframe-designer→lean-experiments-specialist - Module renamed:
_designos→_vortex
What happens:
- Old workflows preserved in
_bmad/bme/_vortex/workflows/_deprecated/ - All 22 Vortex workflows installed
- Config structure updated (preferences preserved)
- 7 agents installed (Emma, Isla, Mila, Liam, Wade, Noah, Max)
npm install convoke-agents@latest
npx -p convoke-agents convoke-update --dry-run # Preview
npx -p convoke-agents convoke-update # ApplyEvery update creates a backup before making changes:
- Location:
_bmad-output/.backups/backup-{version}-{timestamp}/ - Includes: config.yaml, agents, workflows, agent-manifest.csv
- Retention: Last 5 backups kept automatically
- Rollback: Automatic if migration fails
- All user-generated files in
_bmad-output/ - User preferences (name, language settings)
- Custom configuration values
- Agent definition files
- Workflow files (steps, templates, validation)
- Vortex config.yaml (with preference preservation — user-added agents and workflows are kept after core entries)
- User guides
All user-generated content in _bmad-output/ (planning artifacts, implementation artifacts, vortex artifacts) works with updated agents without regeneration. When you update from v1.5.x to v1.6.x, your existing artifacts remain valid inputs to both original and new agents.
Artifacts created with earlier agents (Emma, Isla, Wade, Max) were not designed specifically for the newer agents (Mila, Liam, Noah), but the handoff contracts are backward-compatible by design. A product vision created with v1.5.x works as input to Mila after updating to v1.6.x — the required fields are present.
- Artifact content — Everything in
_bmad-output/(planning artifacts, implementation artifacts, vortex artifacts) - Handoff contract fields — The fields agents produce and consume (HC1-HC5 schemas) are stable across versions
- Workflow outputs — Templates and generated documents maintain their structure
These change between versions but are handled automatically by convoke-update:
- Agent definition files — Persona, menu, and instruction content in
_bmad/bme/_vortex/agents/ - Workflow step files — Step content, templates, and validation in
_bmad/bme/_vortex/workflows/ - Internal file structure — The layout of
_bmad/bme/may change between versions - User guides — Updated guides are installed in
_bmad/bme/_vortex/guides/
You do not need to manually update these — the update system replaces them while preserving your preferences and artifacts.
A previous migration may have crashed. Remove the lock file:
rm _bmad-output/.migration-lock
npx -p convoke-agents convoke-updateOr run npx -p convoke-agents convoke-doctor to diagnose — it detects stale locks.
Restore from backup manually:
# Find your backup
ls -la _bmad-output/.backups/
# Restore (replace {backup-dir} with actual directory name)
cp -r _bmad-output/.backups/{backup-dir}/config.yaml _bmad/bme/_vortex/
cp -r _bmad-output/.backups/{backup-dir}/agents _bmad/bme/_vortex/
cp -r _bmad-output/.backups/{backup-dir}/workflows _bmad/bme/_vortex/npx caches package binaries. If you installed at an older version, convoke-update may keep running the cached script instead of the latest. Force-fetch the latest:
npx -p convoke-agents@latest convoke-updateThis tells npx to download convoke-agents@latest first, then run the convoke-update bin from it.
Reinstall from scratch (preserves user data):
npx -p convoke-agents convoke-install-vortexls -la _bmad-output/.logs/
cat _bmad-output/.logs/migration-*.log | tail -100If you encounter issues:
- Run
npx -p convoke-agents convoke-doctorfor diagnostics - Check migration logs in
_bmad-output/.logs/ - Restore from backup in
_bmad-output/.backups/ - Report an issue — include your version (
npx -p convoke-agents convoke-version) and error message