Feature Request: Unique Naming Constraint for Assistant Instances in the API

I’ve been working with the Assistant API and noticed that every time I run my code to create an assistant, a new instance is generated even if it has the same name as an existing one. This results in multiple assistants with identical names, which can be confusing and clutter the workspace.

Feature Request: I propose the implementation of a unique naming constraint for assistant instances created through the API. If an assistant with the same name already exists, the API could either prevent the creation of a new one or provide an option to update the existing assistant.

At least this way you would have a way to notify the user of what’s going on, and prevent excessive requests coming in from people that are re-running streamlit! :smiley:

Thanks

I used the assistant list to overcome this issue but no harm in requesting :slight_smile: