Warp uses Anthropic API calls instead of OpenAI when using GPT 5.3 Codex extra high reasoning.

[frischeDaten]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

I thought I would use Codecs GPT 5.3 extra high reasoning for my coding task. I noticed that I didn't see any usage against my API keys. Then I got an email from Anthropic that my credits are running out, and now WAP tells me that my credits balance is too low. That comes from Anthropic, so the whole time WAP didn't use my OpenAI key for GPT 5.3 codecs, extra high reasoning, but my Anthropic key.

To reproduce

Put in keys for Anthropic and for OpenAI, then try to use GPT-5.3 Codex Extra High Reasoning. It won't use your OpenAI key but the Anthropic key. I don't know which models it really uses, but it's not Codex, apparently.

Expected behavior

I would expect that it uses the OpenAI infrastructure for Codex and not Anthropic.

Screenshots, videos, and logs

Operating system (OS)

Windows

Operating system and version

10.0.26200.7840

Shell Version

No response

Current Warp version

2026.02.11 (v0.2026.02.11.08.23)

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

I don't know the version.

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

Ignore

[frischeDaten]

I noticed that apparently it always tries to use the Anthropic API. I tried all the Codex variants and also tried Gemini because I also have the Gemini API keys. But it tried again Anthropic also with Gemini. And all the others. So there might be a big issue with API key selection for models that have keys provided.

[szgupta]

Hey @frischeDaten, sorry for the trouble here. Warp got early access to Codex 5.3, but unfortunately that means it'll only work with Warp's Direct API access and not with personal API keys until the model is GA. We can make that clearer in the UI. In the meantime, I would suggest using Codex 5.2 -- let me know if we're still not using your personal API key in that case.