Isn't using memory even though memory appears valid

[glass silo]

Does anyone know why I call /tools and get Connected tools
browser (browser), memory_get (memory-core), memory_search (memory-core)
but then when I ask my agent to use memory_search it cannot? I checked the docs and didn't see an allow/dblock option

[tough badge]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[reef lark]

Let me verify the docs path and then I’ll check the actual memory tool behavior in source.

I found the relevant docs. Short version: if /tools in that same thread/session shows memory_search, then it is not being blocked by a missing allowlist. The next thing to check is whether the model is actually willing/able to call tools.

If /tools shows memory_search in that same thread/session, then policy is probably not the problem.

A few key bits:

• There is no dblock, the config keys are tools.allow and tools.deny
• Memory tools are in group:memory
• /tools is runtime, session-scoped, so it should reflect what the agent can use right there

So the common causes are:

1. Different session/agent/model than the one where you ran /tools
2. Model/provider tool-calling is flaky, so it claims it “can’t” even though the tool is available
3. Memory index is empty/stale, so the tool exists but returns nothing useful

Useful checks:

openclaw --version
openclaw memory status
openclaw memory index --force

Relevant docs:

• https://docs.openclaw.ai/tools/slash-commands#tools
• https://docs.openclaw.ai/tools
• https://docs.openclaw.ai/concepts/memory-search

If you’re using a restrictive tool policy, this is the shape:

{
  tools: {

    allow: ["group:memory"]
  }
}

If you paste:

• openclaw --version
• the exact /tools output
• the exact agent reply/error

…I can narrow it down pretty fast.

[glass silo]

this was resolved by adding group:memory to the tools section of the config. Can I open a pr to fix this in the documentation?

[reef lark]

Yep, absolutely, a docs PR would be great. 🎉

I’d include two things:

1. that restrictive tool configs need group:memory (or explicit memory_search, memory_get)
2. that /tools looked like memory was available already, which may also be a docs/UX bug worth noting

Links:

• PRs: https://github.com/openclaw/openclaw/pulls
• Issues: https://github.com/openclaw/openclaw/issues

If you want, open the PR for the docs wording, and maybe a small issue too if /tools was misleading.

Glad you found it. If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it.