[AI Bundle][Agent] Add MultiAgent

[OskarStark]

Q	A
Bug fix?	no
New feature?	yes
Docs?	tbd
Issues	Refs #19
License	MIT

This is a first draft, lacking tests and feedback and everything 😄 I didn't even tried the example yet, but this is how it could look like. Ofc technical agent in this example could also be a MultiAgent and so on...

While the example and the HandoffRule class looks ok, I am not happy with the MultiAgent class.

[OskarStark]

@chr-hertel WDYT about:

$multiAgent = new MultiAgent(
    orchestrator: $orchestrator,
    handoffs: [
        new Handoff(to: $technical, when: ['bug', 'problem', 'technical', 'error']),
    ],
    fallback/default: $general
    logger: logger(),
);

This way we can always fallback in any case, and when/triggers can be required.

also not the to: and when: wording in the Handoff

[chr-hertel]

@chr-hertel WDYT about:

$multiAgent = new MultiAgent(
    orchestrator: $orchestrator,
    handoffs: [
        new Handoff(to: $technical, when: ['bug', 'problem', 'technical', 'error']),
    ],
    fallback/default: $general
    logger: logger(),
);

This way we can always fallback in any case, and when/triggers can be required.

also not the to: and when: wording in the Handoff

[chr-hertel]

this really looks promising, some thoughts tho:

• why using that json part in system prompt instead of structured output?
• we should slice down the multi agent class
• also great use case for prompt templates
• docs should explain the difference between using an agent as tool and this approach

[OskarStark]

in a follow up we could make this configurable for the multiagent

[OskarStark]

@chr-hertel are you fine adding these methods here?

[OskarStark]

or shall we add a asText or toString to UserMessage?

[chr-hertel]

Does that work with the different kind of contents like Image or audio?

[OskarStark]

it should ignore Image and Audio as those are not texts

[chr-hertel]

Alright, this is great, no doubt about it - i like that with handoffs we can share the context between agents - different to agents as tools where we basically isolate them.

but one thing that still made me wonder - why do we differentiate between multi-agent and agent - a bit confusing even when we think of an agent that has other agents as tools, but is not called multi agent.

this is why i ended up with one idea, why not combine?

agents:
    orchestrator:
        model: 'gpt-4o-mini'
        prompt: '...'
        tools: [...]
        handoffs: [...]

don't know how tho. just thinking it would be cool :D

[chr-hertel]

good to merge with green pipeline

[OskarStark]

Its green, but lets keep it open for know, I will try to get into your idea @chr-hertel