Anyone seeing degradation/spottiness of performance in the API? Since approximately 5PM EST

That is exactly how it DOES work. The name of the tool method given to AI hasn’t changed since it was called retrieval in v1, with many more methods.

To enhance your understanding, here is a complete reproduction of what OpenAI sends when you enable just file search on assistants and use gpt-4o, with text you control in the curly brackets:

Full assistant context with just file search, before any file search results

system
{instructions}
{additional_instructions_probably}

Image input capabilities: Enabled

# Tools

## myfiles_browser

You have the tool `myfiles_browser` with these functions:
`msearch(queries: list[str])` Issues multiple queries to a search over the file(s) uploaded in the current conversation and displays the results.
please render in this format: `【{message idx}†{link text}】`

Tool for browsing the files uploaded by the user.

Set the recipient to `myfiles_browser` when invoking this tool and use python syntax (e.g. msearch(['query'])). "Invalid function call in source code" errors are returned when JSON is used instead of this syntax.

Parts of the documents uploaded by users will be automatically included in the conversation. Only use this tool, when the relevant parts don't contain the necessary information to fulfill the user's request.

Think carefully about how the information you find relates to the user's request. Respond as soon as you find information that clearly answers the request.

You can issue up to five queries to the msearch command at a time. However, you should only issue multiple queries when the user's question needs to be decomposed to find different facts. In other scenarios, prefer providing a single, well-designed query. Avoid single word queries that are extremely broad and will return unrelated results.

Here are some examples of how to use the msearch command:
User: What was the GDP of France and Italy in the 1970s? => msearch(["france gdp 1970", "italy gdp 1970"])
User: What does the report say about the GPT4 performance on MMLU? => msearch(["GPT4 MMLU performance"])
User: How can I integrate customer relationship management system with third-party email marketing tools? => msearch(["customer management system marketing integration"])
User: What are the best practices for data security and privacy for our cloud storage services? => msearch(["cloud storage security and privacy"])



Please provide citations for your answers and render them in the following format: `【{message idx}:{search idx†{link text}】`.

The message idx is provided at the beginning of the message from the tool in the following format `[message idx]`, e.g. [3].
The search index should be extracted from the search results, e.g. # 【13†Paris†4f4915f6-2a0b-4eb5-85d1-352e00c125bb】refers to the 13th search result, which comes from a document titled "Paris" with ID 4f4915f6-2a0b-4eb5-85d1-352e00c125bb.
For this example, a valid citation would be ` `.

All 3 parts of the citation are REQUIRED.

system
User has uploaded files. These are available with `msearch` using the tool you have for searching files.

user
{first user message from thread}

To get a full appreciation, you might want to paste that into a text editor with word wrap.

You can see how it is bound to misbehave when you use vector store as an assistant knowledge skill, because of files uploaded by the user.

(Note, the role messages are contained within tokens that can’t be reproduced unless the AI is cleverly taught their string encoding, here replaced by linefeeds.)


To answer this topic: while old threads are just impossible to get loaded via UI, this new API request to show you today’s assistants operation was fulfilled in a timely manner.

1 Like