Runtime recall makes memory a system choice

A Wanderloots tutorial separates a knowledge layer from operational agent memory, then compares always-injected built-in context with a provider that retrieves memory at runtime. The walkthrough uses Hermes, Mnemosyne, and Hindsight as examples. Why it matters: A knowledge base keeps durable material organized and inspectable. Runtime recall changes what enters an agent run without carrying every stored detail in every prompt, but stale preferences or unclear provenance can become invisible defaults.

Try this: For one recurring task, log each recalled item, its source, and the scope that allowed it. Run the same task from a fixed project note, then compare the answer, the injected context, and the review burden before enabling provider recall by default.