How do I review a Zed Authorization header before recovering Montage OAuth?
Zed’s standard remote OAuth prompt is documented without a manually supplied Authorization header. When a copied server example adds one, review that configuration boundary before assuming a missing login prompt means Montage OAuth itself has failed. Review whether a manually configured header intentionally selects an approved auth method. Zed’s standard OAuth route is documented without that header, so copied examples need careful ownership review rather than secret-value guessing.
Help me review a Zed Authorization header before recovering Montage OAuth. Determine whether this connection intends to use Zed’s standard OAuth flow or an existing separately approved authorization method. Request signals_status from Zed Agent and compare the actual workspace with expectations. No writes.Identify the expected auth route
Determine whether this connection intends to use Zed’s standard OAuth flow or an existing separately approved authorization method. Do not inspect or reproduce private header values in the conversation. A configuration review can note that a header exists without exposing its value or implying that every manual authorization method is automatically invalid.
Check for copied header configuration
Review whether context_servers contains a manually supplied Authorization header from another server example. Its presence is not evidence that it is valid Montage access or necessary for standard consent. An example copied from another remote service may intentionally use different auth; its presence alone cannot establish Montage compatibility or an expired grant.
Choose a supported path
Follow the installed Zed documentation to restore the intended standard OAuth configuration when appropriate. Do not guess header contents or combine multiple auth methods merely to make a login prompt appear. Make the intended auth choice explicit before changing configuration, preserving any existing approved method that the account owner deliberately selected.
Return to Zed Agent
Use the remote server’s supported authentication action and review the selected Montage account. Keep ACP and terminal-agent configuration out of this editor-owned recovery workflow. The selected Montage identity should be reviewed through supported consent, not forced by embedding account text in an invented tool parameter.
Verify authorized execution
Request signals_status from Zed Agent and compare the actual workspace with expectations. If auth remains unavailable, retain that blocker instead of presenting a restored prompt or accepted URL as a successful connection. A successful OAuth prompt is an intermediate event; only the subsequent workspace response establishes the checked Zed Agent path’s actual account access.
Keep the boundaries clear.
- Make the intended auth choice explicit before changing configuration, preserving any existing approved method that the account owner deliberately selected.
- A successful OAuth prompt is an intermediate event; only the subsequent workspace response establishes the checked Zed Agent path’s actual account access.
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.