How do I repair the Montage account selected by Codex login?
A Codex server entry may be correct while OAuth selected the wrong Montage account or an expired grant. Recover account access independently of the shared TOML table, keeping CLI and IDE effects visible during diagnosis. The documented login command handles authorization independently of the server table. Check the account returned by the original caller, particularly when both CLI and IDE remain open with different refreshed session states.
Help me repair the Montage account selected by Codex login. Read the actual workspace response or authorization error. Compare signals_status with the expected destination. No writes.Identify the account symptom
Read the actual workspace response or authorization error. If it names an unexpected workspace, stop before exploring private data or attempting the original research task. An unexpected workspace is sufficient evidence to pause; there is no need to inspect private watchlists to determine whether the account is wrong.
Keep TOML stable
Check the configured Montage URL without replacing a correct remote table. Removing server definitions is not a substitute for resolving the identity selected at consent. The known shared table expresses registration; removing it can obscure the original problem without resolving consent or changing the authorized account.
Use supported login
Use codex mcp login montage when ready to authorize the intended account. Review the consent identity instead of assuming the browser’s current session selects the desired workspace. A documented login command should be used for the registered server name, not accompanied by invented account-selection flags or secret arguments.
Return to the right surface
Revisit the CLI or IDE conversation that needed access and request one status read. Do not assume both surfaces refreshed simply because browser consent completed. The verification prompt should state which surface is being tested so a response from the CLI is not silently attributed to the IDE.
Inspect the recovered workspace
Compare signals_status with the expected destination. If another Codex surface remains blocked, report it separately instead of treating shared configuration as authenticated execution parity. Account recovery success should be stated only for the path that produced the real response, especially when both surfaces remain open simultaneously.
Keep the boundaries clear.
- A documented login command should be used for the registered server name, not accompanied by invented account-selection flags or secret arguments.
- Account recovery success should be stated only for the path that produced the real response, especially when both surfaces remain open simultaneously.
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.