How do I trace a Roo Code project override that hides global Montage settings?
Project-level Roo Code configuration can make a correct global Montage definition seem ineffective. Resolve the active project’s precedence before changing account authorization, preserving both files until you know which entry is actually controlling the affected remote connection. The effective target comes from the winning configuration, not the most familiar file. Inspect project and global definitions together before any auth intervention so a stale override does not masquerade as a Montage outage.
Help me trace a Roo Code project override that hides global Montage settings. Read .roo/mcp.json and the applicable global mcp_settings.json. Use signals_status only with approved authorization. No writes.Inspect both locations
Read .roo/mcp.json and the applicable global mcp_settings.json. Identify montage entries and their differences without immediately editing both or assuming the global definition is authoritative. The comparison artifact can list project and global destinations without exposing secrets, making the winning definition understandable before any account troubleshooting.
Apply documented precedence
A project entry can override the global server for this repository. Check whether a stale project URL explains the behavior before starting repeated sign-in attempts. A correct global entry may legitimately remain unused for this repository; that observation is configuration precedence, not evidence of remote service failure.
Scope the correction
If the project file owns this connection, use the installed Roo release’s remote schema there. Do not transplant transport property spelling from another client’s example. Use Roo’s own release documentation for transport properties instead of guessing from Cline or Continue examples that spell remote types differently.
Qualify auth independently
After identifying the effective entry, check whether this Roo version supports Montage authorization. Resolving project precedence cannot turn remote transport support into compatible OAuth capability. Even after the project URL is corrected, compatible Montage authorization still needs an independent approved path before private tool execution can proceed.
Report the resolved layer
Use signals_status only with approved authorization. Otherwise say configuration ownership is understood while workspace execution remains blocked; a correct global URL alone is not success. State “effective target resolved, execution blocked” when appropriate rather than turning successful configuration inspection into an unsupported connection claim.
Keep the boundaries clear.
- Use Roo’s own release documentation for transport properties instead of guessing from Cline or Continue examples that spell remote types differently.
- State “effective target resolved, execution blocked” when appropriate rather than turning successful configuration inspection into an unsupported connection claim.
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.