# Codex suggests deprecated API (Assistants ➜ Responses) — anyone found a reliable workaround?

**URL:** <https://community.openai.com/t/codex-suggests-deprecated-api-assistants-responses-anyone-found-a-reliable-workaround/1361734>\
**Category:** Codex\
**Tags:** codex, gpt-5-codex\
**Created:** [October 9, 2025, 4:11pm UTC](https://community.openai.com/t/codex-suggests-deprecated-api-assistants-responses-anyone-found-a-reliable-workaround/1361734 "2025-10-09T16:11:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jose.consciencia](https://avatars.discourse-cdn.com/v4/letter/j/977dab/32.png) [@jose.consciencia](https://community.openai.com/u/jose.consciencia)\
**Post date:** [October 9, 2025, 4:11pm UTC](https://community.openai.com/t/codex-suggests-deprecated-api-assistants-responses-anyone-found-a-reliable-workaround/1361734/1 "2025-10-09T16:11:15Z")

</div>

While refactoring an internal tool from the deprecated Assistants API to the Responses API using the Codex VS Code extension (model: gpt-5-codex medium), Codex repeatedly suggested removed/renamed parameters and JSON schemas that failed validation against the latest API. Has anyone figured out how to get Codex to rely on current API/library documentation?

---

<div class="post-metadata">

**Author:** ![magnusmatias](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/magnusmatias/32/511259_2.png) [@magnusmatias](https://community.openai.com/u/magnusmatias)\
**Post date:** [October 9, 2025, 5:07pm UTC](https://community.openai.com/t/codex-suggests-deprecated-api-assistants-responses-anyone-found-a-reliable-workaround/1361734/2 "2025-10-09T17:07:55Z")

</div>

Same here.  
I have not found out how to make it use web search, which sometimes helps chatgpt against outdated info.