Robert Ta praises OpenAI's documentation for naming the agent architecture builders have used for a year: an orchestration agent that interprets user intent and routes requests to specialist agents. This pattern is now becoming the standard for multi-agent systems.
One thing I'd say is kudos to the OpenAI team to make this developer documentation page easy to read. I also really love this terminology at the start here. You have this like really nice quick start. You can easily link to things. I thought it was also interesting that they've like named particular agent cases. Like you would probably want some sort of specialist agent. So if you have a bunch of specialist agents, then you need an orchestration agent. And they've sort of codified it here in my mind where for the last year AI builders have known this to be a problem. Which is when a user talks to your agent interface, like whatever it looks like on the UI/UX affordance, then there's going to need to be a layer which is what is the user trying to do? And obviously if they're trying to do many things in your particular domain across your workflows, you would need to hand that off to the right agent to handle that and with the right harness. So it's becoming clear, like you need a harness around the orchestration layer and that, that's becoming codified best practice. That's, that's something else that I thought was cool.
