Documentation

124 tools, 24 guides — and you need about three of them. Search everything at once, or pick the sentence that sounds like your problem.

Remember & recall

21 tools

“I want my AI to remember what we already figured out”

The core loop: store a lesson once, get it back the next time it matters — in any editor, in any session.

  • learn_from_attempts

    Store a lesson AFTER any non-trivial task (deploy, debug, fix, decision); future sessions recall it.

  • smart_recall

    Returns the fixes, decisions and pitfalls this team already learned for the task at hand.

  • recall_feedback

    Tell the Brain whether a recalled lesson ACTUALLY SOLVED your problem.

Start & end a session

7 tools

“I want to pick up exactly where the last window left off”

One call in, one call out. The next session opens pre-briefed instead of asking you to explain the project again.

  • session_start

    Single-call session briefing. Call this at the START of every session INSTEAD of multiple separate smart_recall/recall_best_solution calls.

  • session_end

    Save a session summary when you finish working. Records what was accomplished, files changed, and lesson count.

  • session_handoff

    Save a detailed handoff for the NEXT chat window / session.

Understand a codebase

10 tools

“I want the AI to know this repository, not just my prompt”

Turn the repo itself into memory: which files belong together, what depends on what, and who has touched it before.

  • index_project

    Index local source files into the cachly semantic cache so AI assistants can use semantic_search to find relevant files instead of re-reading the whole codebase every time.

  • brain_file_map

    Show what cachly knows about a list of files — experts + related lessons per file.

  • brain_service_map

    Map everything the Brain knows about a running service or system: who operates it, which files run in it, every known failure, and every proven fix.

Share with your team

17 tools

“I want what one colleague learns to reach everyone else”

A shared brain with roles and scopes: your teammate debugs it once, you recall the answer.

  • team_learn

    Store a lesson in a shared team brain so all team members benefit. Like learn_from_attempts, but REQUIRES an author name for attribution.

  • team_recall

    Recall lessons from a shared team brain, showing who learned what. Works on any shared instance (all team members using the same instance_id).

  • team_confirm

    Endorse (review-confirm) a team lesson so trusted, human-reviewed knowledge ranks above unreviewed auto-learned entries.

Predict & plan

10 tools

“I want to know what usually goes wrong before I do it”

Ask the brain first: known failure patterns for this change, contradictions between lessons, and what is next on the plan.

  • brain_predict

    READ-ONLY — no side effects, no writes, no external network calls.

  • brain_predict_failures

    Pre-deploy failure prediction with probability percentages. Given a change context (e.g.

  • brain_plan

    READ-ONLY — no side effects, no writes, no external network calls. Generative planning layer on top of the CKG: given a task you are ABOUT to do (e.g.

Cache data & LLM answers

17 tools

“I want to stop paying for the same answer twice”

The managed cache underneath it all: Valkey, Redis or Dragonfly, with semantic lookup for LLM responses.

  • cache_get

    Get a value from a running cache instance by key. Returns the stored value (string or deserialized JSON object) or null if the key does not exist or has expired.

  • cache_set

    Set a key-value pair in a running cache instance. Overwrites any existing value at the key — not idempotent for new data.

  • cache_delete

    Permanently delete one or more keys from a running cache instance (uses Redis DEL).

Keep the brain healthy

14 tools

“I want to check the memory is still worth trusting”

Memory rots quietly. These measure it, clean it, and keep feeding it from git and CI without anyone typing.

  • brain_doctor

    Check the health of your AI Brain and get actionable recommendations. Reports: lesson count, context entries, last session age, open failures, quality score, effective IQ boost, stale index.

  • brain_hygiene

    Autonomously sweep and maintain your Brain — flags stale lessons as provisional, archives long-dormant ones, and resolves contradictions where success clearly dominates failure.

  • brain_metrics

    Report the three decisive Brain metrics: (1) time-to-first-recall (onboarding friction), (2) recall-lift vs.

Reach beyond your team

21 tools

“I want lessons that nobody in my company has learned yet”

Publish, import and federate knowledge — including a privacy-preserving mode that shares the signal without the details.

  • fedbrain_search

    FedBrain context-weighted search: Search the global commons, weighting results by tech-stack similarity.

  • fedbrain_contribute

    FedBrain (Layer 6): Contribute a lesson to the global Knowledge Commons with a cryptographic knowledge certificate.

  • fedbrain_confirm

    Confirm that a syndicated lesson from the global commons worked for you.

Set up & connect

7 tools

“I want to get this running in my editor”

Instances, connection strings and the one-shot wizard that writes the config for Claude Code, Cursor, Copilot and Windsurf.

  • setup_ai_memory

    One-shot setup of the cachly 3-layer AI Memory system for a project.\n\nLayer 1 — Storage: your cachly instance (Valkey, persistent across sessions)\nLayer 2 — Tools: learn_from_attempts +…

  • create_instance

    Create a new managed Valkey/Redis cache instance on cachly.dev. Free tier provisions in ~30 seconds.

  • list_instances

    List all your cachly cache instances with their status and connection details.

All guides

24 pages

The long-form pages, when a single tool is not the answer.

AI Memory — 3-layer systemNewThe setup wizard and the learn / recall loop that gives an assistant persistent memory.UserPromptSubmit hookNewGive Claude Code a memory: what the hook receives, how additionalContext works, a working Node script and five traps.Lessons learned for coding agentsNewWhat to write down so the next session uses it: symptom, decisive fact first, dead ends, files, a check. Real examples and a LESSONS.md template.Claude Code hooksNewEvery hook event by when it fires: what SessionStart, UserPromptSubmit, PreToolUse and Stop can block, add and change.EU hosting and your dataNewWhat leaves your machine, where it lands, the network edge, and a checklist to verify it yourself.cachly vs SupermemoryNewHosting, MCP, Claude Code hooks, license and pricing side by side, each row with its source.cachly vs ZepNewMemory model, MCP access, self-hosting, compliance and pricing side by side, each row with its source.cachly vs claude-memNewTwo memories for Claude Code: hooks, where memory lives, which model writes it, teams and pricing.cachly vs Basic MemoryNewLessons or Markdown notes: storage, search, Claude Code, license and pricing, each row with its source.cachly vs mem0NewMemory model, both Claude Code plugins, MCP server, self-hosting and pricing side by side, each row with its source.cachly vs LettaNewMemory for your assistant or an agent with its own memory: MCP, models, hosting, teams and pricing, each row sourced.MCP integrationConnect Claude, Cursor, Windsurf or Copilot. Provision instances in natural language.IDE pluginsNewVS Code and IntelliJ: see what your AI learned, recall counts and token savings in the status bar.JetBrains plugin guideWhat the plugin does, and how Claude Code, Junie or AI Assistant get the Brain over MCP.API referenceInteractive OpenAPI browser for the full REST API.Recall benchmarkNewOpen methodology and results — including what the CI gate cannot catch, and the two retrieval bugs it missed.Memory crystalsCompress old sessions into distilled wisdom without losing the lessons underneath.Knowledge hubSemantic search across everything your team has learned.Model-neutralSame brain in any AI editor. No vendor lock-in.Semantic cachingVector similarity lookup with multimodal support for text, images and audio.Cache enginesDragonfly, Valkey and Redis — which engine fits which workload.Cluster modeHorizontal scaling with Valkey Cluster: automatic sharding and failover.Agents SDKA caching layer built for agent loops, tool calls and chain-of-thought.Terraform providerManage instances, keys and tiers as code.