Zed
How to fix Zed requests that never reach AI Code With
Saving the provider is not the same as sending traffic to AI Code With. Zed can have several providers at once. Whichever model the Agent Panel has selected is the upstream. If the selection is still built-in OpenAI or a Zed-hosted model, usage records stay empty.
Start with these checks
The Agent Panel selected the wrong provider, or only language_models.openai.api_url was changed, so traffic never reached AI Code With.
- No matching AI Code With usage record appears after sending, or traffic still hits official OpenAI / Zed-hosted models.
- The Agent Panel dropdown is still on built-in OpenAI, Anthropic, or a Zed-hosted model
- Open the Agent Panel model dropdown and find the model under the AI Code With / aicodewith group
01
Use usage records to see where the request went
Send a short, easy-to-spot message from the Agent Panel, then open AI Code With usage records and search by send time and model ID. A record means the relay received the call; no record means Zed sent it somewhere else.
Do not treat “copied” or “provider saved” as a successful connection. The only checkable signals are a normal model reply and a matching usage-record entry.
02
Explicitly select the AI Code With model in the Agent Panel
Open the model dropdown and confirm the highlighted entry is the model you added under openai_compatible, not OpenAI, Anthropic, Copilot, or a Zed-hosted model. New threads sometimes fall back to the last built-in model.
If there is no AI Code With group in the dropdown, go back to Agent Settings and confirm Add Provider and Add Model both finished. A provider without models cannot be selected from the panel.
- 1Open the Agent Panel model dropdown and find the model under the AI Code With / aicodewith group
- 2Select the Model ID you just added (for example deepseek-v4-flash), not a built-in OpenAI model
03
Confirm built-in OpenAI was not overwritten
In settings.json, api_url and available_models should appear under language_models.openai_compatible.aicodewith. If you changed language_models.openai.api_url, restore the official default so it does not compete with the custom provider.
Send another message after fixing the selection. A usage-record row with the matching model and timestamp means the request reached AI Code With. If you then get 401 or Model Not Found, follow those articles instead.
- 1Select the Model ID you just added (for example deepseek-v4-flash), not a built-in OpenAI model
- 2Confirm LLM Providers contains a separate OpenAI-compatible entry whose API URL is https://api.aicodewith.ai/v1
Keep the API key in the Zed provider UI / system keychain. A real key in settings.json is unsafe and can also prevent the UI value from applying.
If it is still not fixed
Sources
Reconfigure
Return to the integration center and continue the setup steps.
Return to the related setup step