How do I audit OpenCode v2 Montage nesting before changing authentication?
A stale OpenCode layout can hide a server even when the URL is correct. Review the documented v2 mcp.servers boundary first, avoiding duplicate legacy entries and keeping schema investigation separate from remote OAuth sign-in or actual workspace execution. For a compatible v2 app, the expected entry lives under mcp.servers. Resolve stale legacy nesting first so later listing, sign-in and status observations can be attributed to one intended remote registration.
Help me audit OpenCode v2 Montage nesting before changing authentication. Review the project’s OpenCode version and schema before treating a v2 example as applicable. After approved OAuth, request signals_status from the active OpenCode session. No writes.Identify the installed generation
Review the project’s OpenCode version and schema before treating a v2 example as applicable. An older configuration needs its matching documentation rather than a silent whole-file rewrite. The generation record should identify whether v2 guidance applies before interpreting legacy syntax as a defect in an older supported environment.
Inspect the nesting
For v2, locate montage under mcp.servers and confirm its remote type and URL. A direct legacy mcp.montage entry does not express the documented layout used here. The review target is the nested remote entry, not a global rewrite of unrelated OpenCode configuration simply to resemble the smallest documentation example.
Resolve duplicates deliberately
Compare any old and new entries before selecting the intended registration. Do not leave both as competing guesses about which endpoint or authorization state the application will use. If both layouts are present, compare them explicitly so later operators can tell which one actually supplied the observed endpoint and account state.
Inspect registration evidence
Use opencode mcp list to check the loaded server, then /mcps for supported sign-in controls. Listing confirms registration, not permission for the intended workspace operation. The list command supplies registration evidence, whereas the in-app sign-in flow addresses account access; neither alone replaces an authorized workspace response.
Verify the effective entry
After approved OAuth, request signals_status from the active OpenCode session. Record whether v2 nesting resolved availability or exposed a separate auth blocker rather than merging those outcomes. The final result should say whether the original server became available or a later auth issue remains, keeping those improvements separately attributable.
Keep the boundaries clear.
- If both layouts are present, compare them explicitly so later operators can tell which one actually supplied the observed endpoint and account state.
- The final result should say whether the original server became available or a later auth issue remains, keeping those improvements separately attributable.
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.