Codex desktop reports Fixture auth as Unsupported while CLI reports not logged in

What version of Codex are you using?

• Codex CLI 0.149.1 on macOS Apple Silicon
• Codex desktop app

What issue are you seeing?

Fixture is configured as an enabled streamable HTTP MCP server at https://beta-api.fixture.app/api/mcp. Its OAuth state is inconsistent across Codex surfaces:

• In Desktop /mcp, a fresh task shows fixture as Enabled with Auth unsupported.
• Earlier in the same debugging session, /mcp showed the same server as Authenticated (OAuth) immediately after successful codex mcp login fixture, but tasks still did not receive Fixture MCP tools.
• In a freshly started CLI 0.149.1 session outside the sandbox, startup reports that the fixture MCP server is not logged in and asks to run codex mcp login fixture.

codex mcp get fixture reports the expected enabled streamable HTTP configuration and URL.

Steps to reproduce

1. Configure Fixture as the streamable HTTP MCP server above.
2. Run codex mcp login fixture and complete OAuth successfully.
3. Open a new Desktop task and run /mcp.
4. Observe fixture as Auth unsupported; Fixture tools are not injected into the task.
5. Start a fresh CLI session and observe the contradictory not-logged-in startup message.

Expected behavior

After successful Fixture OAuth, Desktop and CLI should agree that it is authenticated and Fixture tools should be available in new tasks. Auth unsupported should not replace a successful OAuth state.

Additional information

No private logs or screenshots attached. This occurred after updating to CLI 0.149.1 and fully restarting Codex.

Start by comparing codex mcp login fixture, codex mcp get fixture, Desktop /mcp, and a fresh CLI session using the reproduction steps. Trace where each surface reads the OAuth state and reports authentication; done means both surfaces agree after login and Fixture tools appear in new tasks.