Skip to main content
The V2 OCX product maintains no runtime plugins. The four former plugins remain available to legacy V1 users through frozen registries and repository history. They are not compatible V2 implementations. These are product cuts, not a claim that V2 reproduces every feature. Existing instructions that refer to delegate, delegation_read, plan_save, or custom worktree tools need review. Native OpenCode documentation defines the current tools and configuration. OCX also removes native config mirroring, component config patches, npm dependency installation, launch-time merged overlays/caches, per-file project include/exclude filters, project-selected profiles, adaptive installation roots, and terminal title management. Native V2 handles configuration loading; OCX retains profile selection and file ownership. Named portable profiles and file-owned registry installation remain OCX’s scope. Native configuration directories and skill discovery alone do not provide the same profile lifecycle, package receipts, edit protection, or registry authoring workflow.

​
Legacy continuity

Use OCX 2.0.15 with OpenCode V1. Existing registry URLs and schema URLs remain pinned to their legacy meanings. The new catalog and schema URLs are separate. No published npm package is unpublished, and old tags/releases remain available. Facade retirement follows this order: publish V1-only notices, disable source synchronization, then archive the four repositories. Archiving preserves read access and history. The validation record tracks delivery status; a source PR alone does not mean public deployments or archiving have occurred. Third-party V2 plugins remain supported through native OpenCode configuration. OCX’s retirement does not restrict them.

​
Keep useful instructions

Retiring a runtime plugin does not make its written guidance worthless. All removed agent bodies, command templates, skill guides, and profile notes are preserved as readable Markdown under legacy/docs/ in this repository. You can also browse the frozen source. The full legacy website manual remains in the navigation. When adapting an old definition, separate its useful task instructions from calls to plugin-specific tools. For example, review criteria can remain useful while delegation_read or plan_save instructions need to be removed or rewritten for the native workflow. The V2 catalog’s code-review skill retains a full review method without requiring those retired tools.

​
Migration checklist

  • Check native background work, notification preferences, and worktree workflows against the behavior you actually use.
  • Remove retired package entries and local runtime plugin files from the new setup; renaming their config key does not port their implementations.
  • Review agents and commands that depend on custom delegation, planning, or worktree tool names.
  • Keep valuable skills and supporting files together when copying them.
  • Use the import report to see omissions before creating the new profile.
  • Retain V1 files and a V1 executable until the replacement workflow is verified.
The native migration guide covers OpenCode’s own config compatibility, terminal settings, plugin API, and server/client API changes. OCX’s migration has a narrower role: profile storage, file ownership, and explicit import decisions.