Building an Assistants API UI Wrapper

Hey OpenAI community!

I’ve been working on implementing OpenAI’s Assistants API into a user-friendly interface!

I’ve been developing a platform called MyChatbots.AI, which is essentially a UI wrapper around the Assistants API. The goal was to make it easier for non-technical users to create, train, and deploy AI chatbots using OpenAI’s powerful language models and similarly use them to ChatGPT and enable them to be embedded as chat widgets on their sites.

Since I started using AI, I have believed that context is key to successfully using AI both in our personal lives and in business. Generic responses are great for many end goals, but for me key has always been the ability to train AI on my data and knowledge, so the Assistants API was a godsent.

However, the playground UI wasn’t very useful:

  • I kept losing conversations as they are not stored (to my knowledge anyway)
  • There’s no way to keep track of conversations
  • Managing files was taking more time and effort (IMO) then needed

This triggered me to build MyChatbots.AI for my personal use, and later decided to release it as a SAAS as a few of my business friends kept asking for it.

A few questions for you here:
What are your experiences with handling multi-turn conversations using the Assistants API? Any tips for maintaining context effectively?

How are others handling the challenge of explaining AI capabilities and
limitations to end-users who might not have a technical background?

Looking forward to your responses!

Cheers,
Aron

1 Like

Hey Aron

sorry i was curious did not see another place to ask this:

Can your Mychatbots have multiple assistants taking input from the output of other assistants?

so i could have something like this

“give me some ideas” → ideas assistant → writer assistant → editor assistant (if good say “good”, if not give improvement suggestions ->writer assistant
etc