I can’t be the only one wishing to upload a file at a Thread level!
It’s quite rational to assume there will only be a single file discussed during a single thread. However, currently I need to upload the file during each new message request, which can be long and cumbersome (and add to response time).
At the moment, the only other alternative is uploading a file at assistant level feels too broad! I don’t want to have to create a new assistant for each new thread.
If I upload a file in the first message of the thread, will the retrieval quality drop as the number of messages increases in the thread?
Also, what happens when we start dropping the starting messages when the context length maxes out?
As a future enhancement to consider, it would be great to be able to attach files to threads directly, or retroactively to messages. A particular use case right now is with a function tool call, where I often want to have it attach files that retrieval or code interpreter can therefore process (e.g. a “query our financial database” tool, which dumps a csv in the thread, which Code Interpreter analyzes and charts). There’s no way to do this now that isn’t clunky, as right now the API seems very limited to a straight ChatGPT use case of “user uploads file and types a message to go with it”.
Bumping this thread to find out more about the question regarding retrieval quality. Are files attached on the assistant level vs thread level using the same process for retrieval?