How do I separate Inspector proxy access from Montage authorization?
Inspector may have a protected local proxy as well as a remote Montage account challenge. Diagnose those two boundaries independently so local access errors do not trigger remote credential changes and remote rejection does not lead to disabling the proxy’s own security. Keep the local proxy credential domain separate from the remote Montage account. A local interface becoming reachable does not establish approved workspace access, and a remote rejection cannot justify disabling protection around the diagnostic tool itself.
Help me separate Inspector proxy access from Montage authorization. Read whether the failure concerns reaching Inspector’s local interface or executing a Montage workspace tool. Report the actual remote response or remaining auth blocker without exposing secrets in screenshots or transcripts. No writes.Identify which boundary rejected access
Read whether the failure concerns reaching Inspector’s local interface or executing a Montage workspace tool. Preserve the stage without printing local proxy tokens or remote access material. The stage record should distinguish local interface access from the remote account call without reproducing either proxy secrets or private authorization headers.
Keep local protections intact
Use the installed Inspector’s documented proxy access method rather than disabling its controls. A successful local UI connection only proves access to the diagnostic tool, not the remote workspace. Disabling the local proxy guard would expand the risk of the diagnostic while doing nothing to establish the Montage account’s approved workspace permission.
Review remote auth support
Configure approved Montage authorization through the Inspector workflow actually in use. Do not assume a browser session, another client’s login or a proxy token grants the remote account permission. Supported remote consent must be evaluated for the selected Inspector setup, not inferred from an unrelated signed-in browser tab or another tool’s token.
Test the remote stage separately
Once local access and supported remote auth are established, inspect tools and select signals_status. A local proxy success or metadata listing cannot substitute for account-scoped execution. Discovering the status definition through the proxy is useful intermediate evidence, but the real read still needs its own successful account-scoped response.
Record both outcomes accurately
Report the actual remote response or remaining auth blocker without exposing secrets in screenshots or transcripts. Never describe weakened local proxy security as a legitimate recovery for Montage authorization failure. An unresolved remote rejection should remain a remote auth blocker even when local proxy access works, preserving both boundaries clearly in the handoff.
Keep the boundaries clear.
- Supported remote consent must be evaluated for the selected Inspector setup, not inferred from an unrelated signed-in browser tab or another tool’s token.
- An unresolved remote rejection should remain a remote auth blocker even when local proxy access works, preserving both boundaries clearly in the handoff.
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.