Why? Because of this announcement of OpenAI.
We’re making improvements to how you build assistants and use tools with the OpenAI API. Based on your feedback from the Assistants API beta, we’ve built the Responses API — a faster, more flexible, and easier way to create agentic experiences that combines the simplicity of Chat Completions with the tool use and state management of the Assistants API. To start, the Responses API will support new built-in tools like web search, file search, and computer use. You can read more about Responses and these new tools in our blog post.
Here’s what this means for the Assistants API:
Feature parity between Responses and Assistants: We’re working on bringing key Assistants API features — like support for Assistant-like and Thread-like objects, plus the Code Interpreter tool — into the Responses API. Deprecation timeline: Once parity is reached, we will announce the deprecation of the Assistants API in the first half of 2026 with 12 months of support from the deprecation date so you have ample time to migrate. Migration support: When we announce the deprecation date, we’ll also provide a comprehensive migration guide to help you move smoothly to Responses, with full data preservation. No immediate changes: The Assistants API will continue to be supported in the near term, and we’ll continue to add new models to it. We’re planning deprecation in 2026, but we’ll follow up again to give you notice of the full plan.
After this announcement I started with the update of my template.
Now you can create agents, activate a Websearch for each agent and you and your users are able to chat with the web. This feature gives you endless possibilities for your Web research.
The template is lightning fast on Chrome with a Lighthouse score of 79.
