How do I reconcile legacy OpenCode instructions with the v2 remote layout?
Old project instructions may place Montage directly under mcp while the installed OpenCode expects mcp.servers. Plan a narrow registration transition that preserves unrelated settings and does not claim that a schema change also migrates account authorization. The transition should be conditional on the actual installed generation. Preserve unrelated settings, choose one registration method and keep private authorization storage separate from any public illustration of the v2 remote layout.
Help me reconcile legacy OpenCode instructions with the v2 remote layout. Determine which configuration generation the current app actually accepts. Request signals_status through the active entry after approved auth. No writes.Compare recipe and installed version
Determine which configuration generation the current app actually accepts. Do not alter an older application solely because a newer documentation page shows a different server layout. The transition plan should state whether the app actually expects v2, preventing current documentation from becoming an accidental upgrade requirement for an older project.
Map only the Montage entry
Identify the old definition’s endpoint and intended use before expressing it in v2. Preserve surrounding settings and do not carry duplicate direct and nested entries as alternative guesses. Record the old endpoint and intended owner before moving the entry, so the migration does not silently replace another server with the same name.
Use one registration method
For compatible v2, choose documented command registration or the mcp.servers JSON form. These express remote intent; they are not two independent servers that both need authorization. Choose command registration or JSON registration as one remote intent; performing both should not be presented as independent required setup stages.
Recheck sign-in separately
Inspect registration with opencode mcp list and use /mcps when consent is required. Do not move private auth storage with the configuration or infer that a layout change preserved every grant. Private grant storage should remain outside the migration artifact, and registration listing should not be treated as proof that consent carried across layouts.
Validate the transitioned path
Request signals_status through the active entry after approved auth. Record the installed generation and real response, leaving other versions or environments unverified instead of claiming a universal migration result. The acceptance note should identify the effective v2 entry and actual call result rather than a successful JSON parse or an untested revised instruction.
Keep the boundaries clear.
- Choose command registration or JSON registration as one remote intent; performing both should not be presented as independent required setup stages.
- The acceptance note should identify the effective v2 entry and actual call result rather than a successful JSON parse or an untested revised instruction.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.