How your agents remember, validate, and self-heal. Every fact passes through 3 layers of protection before it becomes a memory. No duplicates, no contradictions, no garbage.
Every message goes through classification, filtering, the LLM, and a tool loop before responding. Click any step for details.
Every potential memory passes through 3 deduplication layers before being written. No silent duplicates, ever. Click a layer for details.
If Layer 3 can't decide within 3 seconds, the memory is queued for nightly batch processing. The system never silently creates duplicates.
Before any memory writes about the user, it's cross-checked against USER.md — the single source of truth. Prevents hallucinated facts.
USER.md is a protected identity file that only the user can edit. Before writing any memory that references personal facts (family, preferences, identity), the system compares the new claim against USER.md. Contradictions are rejected.
Your agents can suggest updates to your profile but can never modify it themselves. This prevents AI hallucination from corrupting your identity. Only you can change who you are.
A memory's journey from extraction to injection back into the prompt. Click any step for details.
Three active storage layers, each with a specific purpose. R2 file storage is removed — D1 is the source of truth. Click any card for details.
Agents use three tools to manage memories. Inspired by the Letta pattern — agents can update and forget, not just add. Click any tool for details.
Traditional chatbots can only add memories. Your agents can also correct outdated information and remove irrelevant facts. This keeps the memory store clean and accurate over time — not just growing indefinitely.
Two cron jobs run every night to process deferred decisions and consolidate memory. Your agents maintain themselves while you sleep.
Unlike traditional AI where memory degrades or fills with garbage, ZeroBot's nightly self-healing means your agent's memory improves with age. Stale facts fade, contradictions resolve, and duplicates merge — automatically.
Your agents share a common memory pool via D1. When one learns something, all can recall it. Create as many agents as you need — these four are examples.
A Customer Support agent. A Recruiter agent. A Legal Review agent. Whatever your business needs — create it, name it, and it immediately joins the shared memory pool. When one agent learns something, the whole team knows.