Hacker News Reader

Comment by jasongill | Hacker News Reader

I wish OpenAI would provide more clarity about the Assistants API deprecation, which has been announced as being sunset in spring of 2026 and replaced by the Responses API, but still no other updates on the timeline or migration plan.

Prior to the release of the Responses API, the Assistants API was the best way (for our use cases, at least) to interact with OpenAI's API, so hopefully some clarity on the plan for it is released soon (now that Responses API has some of the things that it was previously missing)

View on HN

I hear you and really appreciate the patience here.

We're almost ready to share a migration guide. Today, we closed the gap between Assistants and Responses by launching Code Interpreter and support for multiple vector stores in File Search.

We still need to add support for Assistants and Threads objects to Responses before we can give devs a simple migration path. Working on this actively and hope to have all of this out in the coming weeks.

Interesting that you're migrating assistants and threads to the responses API, I presumed you were killing them off.

I started my MVP product with assistants and migrated to responses pretty easily. I handle a few more things myself but other than that it's not really been difficult.

On the announcement page they are saying that "...introducing updates to the file search tool that allow developers to perform searches across multiple vector stores...". On the docs, I still find this limitation: "At the moment, you can search in only one vector store at a time, so you can include only one vector store ID when calling the file search tool."

Anybody knows how searching multiple vector stores is implemented? The obvious plan would be to allow something like:

  "vector_store_ids": ["<vector_store_id1>", "<vector_store_id2>", ...]

sorry about the error in the docs. we're removing that call out.

`"vector_store_ids": ["<vector_store_id1>", "<vector_store_id2>"]` is exactly right. only 2 vector stores are supported at the moment.

2 feels quite arbitrary and honestly not that much of an improvement. Any plans to up that limit?

we were using it for our agent in https://www.definite.app/ and I've been expecting it to die for almost a year considering the lack of updates.

We switched over to https://ai.pydantic.dev/ which I really like. LLM agnostic and the team is very receptive to feedback.

Reply on news.ycombinator.com