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

What version of Codex are you using?\n\n- Codex CLI 0.149.1 on macOS Apple Silicon\n- Codex desktop app\n\n### What issue are you seeing?\n\nFixture is configured as an enabled streamable HTTP MCP server at . Its OAuth state is inconsistent across Codex surfaces:\n\n- In Desktop , a fresh task shows as Enabled with .\n- Earlier in the same debugging session, showed the same server as immediately after successful Authorize fixture by opening this URL in your browser:

https://beta-api.fixture.app/api/oauth/authorize?response_type=code&client_id=mcp_4TqWFHLIpxFxcLF2fGOgMg&state=4IBF3FgVBlysvNGkyYgl0g&code_challenge=gugHA3CAJXpHgjr3-rF2oceFX167_FJGtTilZYc0ILA&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A61370%2Fcallback%2FF8DUhpXlxJwR&scope=agents%3Aread+agents%3Awrite+crm%3Aread+crm%3Awrite+tasks%3Aread+tasks%3Awrite+users%3Aread&resource=https%3A%2F%2Fbeta-api.fixture.app%2Fapi%2Fmcp

Successfully logged in to MCP server 'fixture'., but tasks still did not receive any tools.\n- In a freshly started CLI 0.149.1 session outside the sandbox, startup reports: .\n\nfixture
enabled: true
transport: streamable_http
url: https://beta-api.fixture.app/api/mcp
bearer_token_env_var: -
http_headers: -
env_http_headers: -
http_headers_helper: -
remove: codex mcp remove fixture reports the expected enabled streamable HTTP configuration and URL.\n\n### Steps to reproduce\n\n1. Configure Fixture as the streamable HTTP MCP server above.\n2. Run Authorize fixture by opening this URL in your browser:
https://beta-api.fixture.app/api/oauth/authorize?response_type=code&client_id=mcp_29Nh0n7g8OD9rdkdsovNow&state=pZF3bXgZ6G6pJ5oTYCcbgw&code_challenge=seuICeqOox_IS6BiFMDRgDk2slJDmReV10YgdlE-oQg&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A61458%2Fcallback%2FF8DUhpXlxJwR&scope=agents%3Aread+agents%3Awrite+crm%3Aread+crm%3Awrite+tasks%3Aread+tasks%3Awrite+users%3Aread&resource=https%3A%2F%2Fbeta-api.fixture.app%2Fapi%2Fmcp

Successfully logged in to MCP server 'fixture'. and complete OAuth successfully.\n3. Open a new Desktop task and run .\n4. Observe as ; Fixture tools are not injected into the task.\n5. Start a fresh CLI session and observe the contradictory startup message.\n\n### Expected behavior\n\nAfter successful Fixture OAuth, Desktop and CLI should agree that it is authenticated and Fixture tools should be available in new tasks. should not replace a successful OAuth state.\n\n### Additional information\n\nNo private logs or screenshots attached. This occurred after updating to CLI 0.149.1 and fully restarting Codex.