Use mutliple assistant ids?

[Unlok-Simon]

This is more of a question than an issue.

Would it be possible to configure multiple Assistants IDs that could then be used by different chat components?

The use case we are looking at would replace the current landing page with the different examples with chats with different assistants.

We were thinking we could change the current assistant-config code to have an array of IDs which we then import into chat components

e.g. The assistant config array would contain (marketing, sales, support). The Marketing chat component would import the array and set the current assistantid = marketing etc....

Just wanted to check that this could work?

Thanks!

[AxfordA]

I am thinking along the same lines. Did you ever work out how to do this?

[Unlok-Simon]

No I couldn't get it to work. Ended up going with different assistants deployed as different instances of the quickstart with a custom UI in front to provide access to them. Not elegant but it worked for the purpose of what we were showing. Being able to easily do this as part of the quickstart would be very useful.

[AxfordA]

Yes, I could understand doing that. I want to pass an assistant_id or a thread_id to the chat page which I think was your original plan. Thanks for coming back to me.

On 08/12/2024 10:34 AM BST Unlok-Simon ***@***.***> wrote: No I couldn't get it to work. Ended up going with different assistants deployed as different instances of the quickstart with a custom UI in front to provide access to them. Not elegant but it worked for the purpose of what we were showing. Being able to easily do this as part of the quickstart would be very useful. — Reply to this email directly, view it on GitHub #22 (comment), or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMVFHAQQJ5KTQ3B6BDPK2DZRB6THAVCNFSM6AAAAABIN6XLXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBTGUYDKOJXGE. You are receiving this because you commented.Message ID: ***@***.***>

+447908 924632 Engineer (noun) - One Who Gets Excited About Things That No One Else Cares About Engineer - I'm Not Arguing, I'm Just Explaining Why I'm Right The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. This message has been sent as a part of discussion between Alan Axford and the addressee whose name is specified above. Should you receive this message by mistake, we would be most grateful if you informed us that the message has been sent to you. In this case, we also ask that you delete this message from your mailbox, and do not forward it or any part of it to anyone else. The contents of this email are the opinion of Alan Axford and should be read as such and are not statements of fact or intended to represent facts. Thank you for your cooperation and understanding.

[tribolil]

How did you create different assistants deployed as different instances of the quickstart with a custom UI in front to provide access?

[AxfordA]

Yes. I have it working but I need to make it a bit cooler. I am using a backend cloud database to hold thread/assistant details that I can re use and train assistant in specific areas of expertise.  On 08/25/2024 1:36 PM BST tribolil ***@***.***> wrote:       How did you create different assistants deployed as different instances of the quickstart with a custom UI in front to provide access? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[tribolil]

So you don’t define the different assistant configurations in this template directly? I’m having issues with making like sub-assistants or even defining the multiple assistant IDs

[AxfordA]

No. I figure each Assistant will be defined and trained for a specific job, say health and safety for example. Then that assistant will be cloned specifically to meet the requirements of a user, say a hospital or a scafolding company (health and safety). The assistant is now becoming an expert in the practise needed by the company. The assistant/expert can now be used to create job related health and safety plans specifically for the company  On 08/25/2024 3:28 PM BST tribolil ***@***.***> wrote:       So you don’t define the different assistant configurations in this template directly? I’m having issues with making like sub-assistants or even defining the multiple assistant ids    Fra: Alan ***@***.***>Sendt: søndag, august 25, 2024 2:59 PMTil: openai/openai-assistants-quickstart ***@***.***>Cc: tribolil ***@***.***>; Comment ***@***.***>Emne: Re: [openai/openai-assistants-quickstart] Use mutliple assistant ids? (Issue #22)   OBS! Mailen er fra en ekstern afsender. Vær opmærksom på links og vedhæftede filer.     NB! This email is from an external sender. Be aware of links and attachments. Yes. I have it working but I need to make it a bit cooler. I am using a backend cloud database to hold thread/assistant details that I can re use and train assistant in specific areas of expertise.  On 08/25/2024 1:36 PM BST tribolil ***@***.***> wrote:       How did you create different assistants deployed as different instances of the quickstart with a custom UI in front to provide access? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***> —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[ozbillwang]

Another improvement for a single use case:

It seems the assistant ID needs to be injected before running npm run build & npm start. Otherwise, the application will prompt for the ID or create a new assistant id during runtime.

Could we make it configurable so that the existing ID is only referenced at startup? This would allow me to easily create multiple instances as a workaround for current issue.