My idea is to develop a proxy assistant that serves as a proxy and decision-maker for specialized sub-assistants, each dedicated to particular tasks and accessible via function calls. However, when the proxy assistant recognizes the need to engage one of these sub-assistants, it encounters an issue:…

Hi Andres First of all, Assistants API is still in beta, so do not expect something fully useable in production. Second, it would be beneficial if you share the code and the logs. In many cases the problem may be in the implementation rather than in the protocol.

How are you implementing the sub-assistants? I am thinking, perhaps you can create an endpoint for each sub-assistant and just call them like an external API.

As in Assistants API an assistant and a run are separate notions, you can do runs with any number of different assistants within one thread. The only problem is these assistants are not aware of each other and consider all previous messages from assistants as their own.

I will break down the reasoning into two concepts to facilitate understanding. My initial idea was to have several assistants operating within the same thread and a proxy assistant that would act as an orchestrator. Each sub-assistant is a function call, so when the proxy assistant identifies the ne…

By function calls. The same thing would happen since I would be trying to start another run in the same thread that is in the “requires_action” state.

So when you try and hit an API in a GPT it asks for permission from the user before it continues. Maybe it’s hanging up, waiting for user authorization? If so, perhaps there is a way you can programmatically respond and move on?

[image] Appertivo: Maybe it’s hanging up, waiting for user authorization? Yeah, sometimes it does. Since my front end is a chat, users can reply to keep the chat going. This is good because it starts a new run. I’ve noticed that sometimes OpenAI cancels a run if it’s taking too long to ‘compl…

Interesting approach! I’ll try it on my use-case. As of now, I’m using the following architecture: Several function specific assistants 1 thread I start with a welcoming assistant which has 1 tool. This tool besides performing the needed action, moves the thread to the next assistant and also up…

Forgive me if I totally misunderstand your problem but why not copy the messages in the thread and create a new thread with those messages to give the sub-assistants to run on?

Sharing another experimental approach for multi-agent workflow for your information and ideation further. azureai-assistant-tool/samples/MultiAgentCodeOrchestration at main · Azure-Samples/azureai-assistant-tool (github.com) In that sample, user communicates with the TaskPlannerAgent (which is usi…

Assistants API Multi Assistant Agentic Workflow

API

dlaytonj2 April 17, 2024, 7:06pm 17

Sorry, wrong thread apologies for the confusion. … Assistants API - Access to multiple assistants

Topic		Replies	Views
Optimal Approach for Managing Chat History in a Multi-Assistant System API gpt-4 , chat-completion , assistants , assistants-api	13	6498	April 11, 2024
Multiple concurrent run same thread Id API	2	1254	May 28, 2024
I need help using assitant in python (required_action infinite loop) API python , assistants-api	12	11379	January 3, 2025
Assistant API using tools from a different assistant API	2	991	April 3, 2024
Assistants API don't allow perform two concurrent runs on same thread API	8	4455	August 12, 2024

Assistants API Multi Assistant Agentic Workflow

Related topics