Symptom
Running crewai reset-memories (for example with --knowledge or -a) inside a crew project fails with 'An unexpected error occurred: No crew found.'
Evidence what you'll see
- Run from inside a newly created crew project
- Same error for several reset flags
Cause
The CLI only found crews defined one way and missed crews created as a direct instance.
Fix steps
0 of 1 done
Your check marks stay in this browser only.
Verify the fix worked
- Run crewai reset-memories -a in the project and confirm it resets instead of reporting no crew.
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