This update includes a fix for assistant-generated files as represented on messages along with an overdue README update reflecting the release status of Azure OpenAI Assistants support.
- Incorporates a specification fix for message image file content that caused generated image file IDs (e.g. from the Code Interpreter tool) to not properly appear in messages
This small release fixes a bug with function tools that use arguments.
- Addressing a related bug,
RequiredFunctionToolCall
has a property replacement:- REMOVED:
Parameters
of typeBinaryData
- ADDED:
Arguments
of typestring
- REMOVED:
- For improved clarity, several types specific to the representation of tool call information in run steps have been renamed with a
RunStep
prefix, better differentiating from request-time tool definitions and model-provided required tool calls:ToolCall
is nowRunStepToolCall
FunctionToolCall
is nowRunStepFunctionToolCall
CodeInterpreterToolCall
is nowRunStepCodeInterpreterToolCall
CodeInterpreterToolCallOutput
is nowRunStepCodeInterpreterToolCallOutput
CodeInterpreterLogOutput
is nowRunStepCodeInterpreterToolCallOutput
CodeInterpreterImageOutput
is nowRunStepCodeInterpreterImageOutput
CodeInterpreterImageReference
is nowRunStepCodeInterpreterImageReference
RetrievalToolCall
is nowRunStepRetrievalToolCall
- Function calls initiated by the model (when a run enters a RequiresAction status involving function tools) will now provide the intended JSON
Arguments
string corresponding to the earlierFunctionDefinition
'sParameters
. The latterParameters
was previously reused within the required action flow, effectively ignoring the properArguments
.
- This is the initial release of
Azure.AI.OpenAI.Assistants
. - Full support for OpenAI's beta Assistants features is included; see OpenAI's documentation for more: https://platform.openai.com/docs/assistants/overview
- Azure OpenAI does not yet feature an
/assistants
endpoint and this library will thus currently only work with theapi.openapi.com
endpoint. Stay tuned!