crewAI icon indicating copy to clipboard operation
crewAI copied to clipboard

[FEATURE] Ability to pass work between crews other than agents

Open Saicheg opened this issue 11 months ago • 8 comments

Feature Area

Agent capabilities

Is your feature request related to a an existing bug? Please link it here.

NA

Describe the solution you'd like

I am really fascinated with the idea of manager agent which can pass worker to different coworkers in order to perform specific tasks.

Lately I've been experimenting on even more advanced workflow, where instead of passing work to agents you can pass it to whole crews.

Unfortunately with current design it is very hard to make it very easy. You can pass jobs to agents, not whole crews. I see this as completely new feature, where you can have some "top manager" to have a task and decide which crews to use for this.

Describe alternatives you've considered

They way I've implemented such behaviour right now is by having each agent in crew with manager one custom tool, which will be called every time and then crew will be called inside of this tool. It works more or less fine, but create unnecessary overhead of passing to worker, then calling tool and etc.

Additional context

No response

Willingness to Contribute

I could provide more detailed specifications

Saicheg avatar Feb 11 '25 10:02 Saicheg

Try incorporating a crew inside a tool, and then some parent agents, with tool capable of kicking off a crew, managed by a parent crew.

Vidit-Ostwal avatar Feb 11 '25 18:02 Vidit-Ostwal

Try incorporating a crew inside a tool and then some parent agents, with a tool capable of kicking off a crew managed by a parent crew.

This is exactly how I am doing it right now, but it creates a lot of overhead and problems with sharing context. Every execution request has to go through DelegationTool -> CustomTool -> Crew. With a really big context windows it takes a big tool.

Saicheg avatar Feb 12 '25 13:02 Saicheg

This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Mar 15 '25 12:03 github-actions[bot]

Adding a comment to keep this issue active.

Vidit-Ostwal avatar Mar 16 '25 12:03 Vidit-Ostwal

This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Apr 16 '25 12:04 github-actions[bot]

Still waiting for someone on crewai team to leave an opinion on this.

Saicheg avatar Apr 17 '25 08:04 Saicheg

Not from the team, but how about using Agent-2-Agent Protocol for this.

Vidit-Ostwal avatar Apr 17 '25 10:04 Vidit-Ostwal

@Vidit-Ostwal i don't think we need a protocol here since it is an internal communication between different parts of system. It is more like a tool call, similar to what is already hapenning with agents having manager.

Saicheg avatar Apr 17 '25 11:04 Saicheg

This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar May 18 '25 12:05 github-actions[bot]

This issue was closed because it has been stalled for 5 days with no activity.

github-actions[bot] avatar May 23 '25 12:05 github-actions[bot]