Codex desktop reports Fixture auth as Unsupported while CLI reports not logged in
Open 💬 2 comments Opened Aug 25, 2026 by ppezaris
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
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
- Configure Fixture as the streamable HTTP MCP server above.
- Run codex mcp login fixture and complete OAuth successfully.
- Open a new Desktop task and run /mcp.
- Observe fixture as Auth unsupported; Fixture tools are not injected into the task.
- 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.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Update and correction: after the user reauthenticated Fixture, one fresh CLI session successfully called fixture.list_pipelines. However, a later fresh CLI session reported: MCP startup incomplete (failed: codex_apps, fixture, linear, yarn).
This makes the behavior intermittent; the CLI is not a reliable workaround. Fixture failed alongside several unrelated MCP servers, which points to a broader MCP startup or timeout problem rather than a persistently expired Fixture OAuth token. Screenshot not attached.