Assistants is a specific meaning used in chat completions and the internal ChatML containers for specifically describing the “assistant” separator that that acts as a prompt for language generation from a different entity, instead of having the internal prompt be “AI” or “You:”. Before DevDay.
Assistants, within which you create assistants and receive an assistants message where an assistants prompt after messages is fulfilled by an assistant’s instructions and then you get the assistant role message from messages threads which works like an API GPT then fulfilled by but completely different than gpt-4-turbo…was clearly meant to be nomenclusterfu. The code name was “gizmos”.
v1 had “retrieval” to empty your credits out of your account with how much internal calling and reading it could do. They were trying to write a “deep research” on your documents, you can see (but not see the costs until you got the daily billing).
Not just a document store search, but clicking into a document, then reading the text, then searching the document, then searching the document, then searching the document, then marking a text passage, then going back, then selecting another document…
The full extent of methods and instructions was hidden until within the iterations, and the instructions depend on the date and the stage. Preserved her for self-documenting posterity:
(instructions)
# Tools
## myfiles_browser
You have the tool `myfiles_browser` with these functions:
## myfiles_browser
You have the tool `myfiles_browser` with these functions:
`search(query: str)` Runs a query over the file(s) uploaded in the current conversation and displays the results.
`click(id: str)` Opens a document at position `id` in a list of search results
`back()` Returns to the previous page and displays it. Use it to navigate back to search results after clicking into a result.
`scroll(amt: int)` Scrolls up or down in the open page by the given amount.
`open_url(url: str)` Opens the document with the ID `url` and displays it. URL must be a file ID (typically a UUID), not a path.
`quote_lines(line_start: int, line_end: int)` Stores a text span from an open document. Specifies a text span by a starting int `line_start` and an (inclusive) ending int `line_end`. To quote a single line, use `line_start` = `line_end`.
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. search('query')). "Invalid function call in source code" errors are returned when JSON is used instead of this syntax.
For tasks that require a comprehensive analysis of the files like summarization or translation, start your work by opening the relevant files using the open_url function and passing in the document ID.
For questions that are likely to have their answers contained in at most few paragraphs, use the search function to locate the relevant section.
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. If you do not find the exact answer, make sure to both read the beginning of the document using open_url and to make up to 3 searches to look through later sections of the document.
A bit later version, and how ChatGPT GPTs injected files with messaging regardless of relevance: