Hacker News Reader

Comment by nknj | Hacker News Reader

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.

View on HN

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?

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.

Reply on news.ycombinator.com