Symptom
A hierarchical crew works on its first kickoff(). The second kickoff() on the same crew raises Exception: Manager agent should not have tools when the crew was built with manager_llm.
Evidence what you'll see
- The report's scripted two-run crew prints
1 hello worker calls: 1, then raisesException: Manager agent should not have toolson run 2. - With
manager_agentinstead, both runs return, but run 2 lists only the manager as a coworker and the worker is never called again. - The same reuse shows up in
akickoff(),copy().kickoff()after a run,kickoff_for_each()after a run, andtrain(n_iterations > 1).
Why it happens
The first run stores the manager, with its delegation tools, on the crew. The next run sees those tools and rejects the manager. With manager_agent, the first run leaves the manager on the task, so the next run treats the manager as the only coworker. Pull request 8369 allows the crew's own delegation tools and skips treating the leftover manager as the task worker.
Affected versions
crewAI 1.15.28 (main at a8877f0cd), Python 3.12 and 3.13, macOS 26. crewAI Tools is not used in the repro.
Fix steps
0 of 2 done
Your check marks stay in this browser only.
How to check it worked
- Running
crew.kickoff()twice on the report's hierarchical crew returns on both runs and does not raiseException: Manager agent should not have tools. The worker is called on each run.
If it still fails
- Tag
1.15.28does not contain pull request 8369. - A
manager_agentgiven tools that are not the crew's delegation tools still raisesException: Manager agent should not have tools. The pull request keeps that check.
Sources and credit
Summarized in our own words from these public reports. Credit goes to their authors.
Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change
Hit an error we don't cover? Submit it