Install

Agent integrations

Migration

Move Pax integrations between editors, machines, or protocol versions without losing user content.

1 min readUpdated

Migrate Pax when you change editors, clone the repository on a new machine, or pull a protocol version bump.

What you will learn

  • User files outside Pax markers are never deleted
  • Protocol adapters regenerate from canonical source
  • Scene and brand documents migrate with explicit schema commands
  • Integration status is always inspectable

Change editors

  1. Check what is installed

    paxfx integrations status

  2. Remove the old editor integration

    paxfx uninstall integrations --yes

    Removes MCP entries and Pax-owned instruction blocks. Your edits outside <!-- pax-instructions-start --> markers stay.

  3. Install the new editor

    paxfx install cursor
# or: paxfx install claude | codex | opencode
paxfx protocol install

Migrate project schema

paxfx migrate project
paxfx migrate scene path/to/scene.json

Writes a backup before mutating. Use --dry-run to preview.

Migrate protocol version

After pulling a Pax update:

paxfx protocol validate
paxfx protocol generate
paxfx protocol parity
paxfx protocol install

Parity must pass before adapters ship. CI runs pnpm check:protocol.

UpgradeRefresh skills and MCP after a Pax update.UninstallRemove Pax cleanly from a project.ProtocolCanonical loop and adapter source.

Was this page helpful?

Edit this page

Answers are not recorded or transmitted. Pax has no telemetry.