.Net: New Feature: OpenAIAssistantAgent's AddChatMessageAsync for files.

[aeras3637]

---

name: OpenAIAssistantAgent's AddChatMessageAsync for files.
Please use OpenAIAssistantAgent's AddChatMessageAsync to correspond to the file.

You may want to upload a file in the middle of an Agent's conversation.
In AssistantMessageFactory.CreateOptions, only Metadata is supported and there is no way to pass FileId.
If FileReferenceContent is included in Items of ChatMessageContent, please set it to Attachments in MessageCreationOptions.

---

[crickman]

Hi @aeras3637, thank you for this suggestion. I'm curious on which type of file you are aiming to upload?

The Assistant API support both text and image content for input messages; although, Azure services / deployments are restricted to text-only.

All other file content must be either referenced from a Vector Store (for the file-search tool) or as a tool resource (for the code-interpreter tool). You may add files to a referenced vector store at any point using the OpenAIFileClient , as shown here:

https://github.com/microsoft/semantic-kernel/blob/main/dotnet/samples/GettingStartedWithAgents/Step11_AssistantTool_FileSearch.cs

Additionally, files specific to a particular thread may be specified upon thread-creation via: https://github.com/microsoft/semantic-kernel/blob/main/dotnet/src/Agents/OpenAI/OpenAIThreadCreationOptions.cs

(Either code-interpreter files, or a Vector Store for file-search).

From a design perspective, we chose to avoid managing , obfuscating, or otherwise interfering with how a developer might defined and update a Vector Store.

In terms of providing file-content to an assistant, we are constrained by what is possible via the API:

https://platform.openai.com/docs/api-reference/assistants

With that said, I'd very much be open to continuing to explore your proposal. Looking forward to your response.