Feature Request: Configurable Default Limit for /recall Command
Problem
The /recall slash command currently has a hardcoded default of 5 memories, which feels limiting for users with dense conversation history. While maxRecallResults controls auto-recall into AI context, the CLI /recall command ignores this setting.
Current Behavior
/recall working with jenny
# Returns: 5 memories (hardcoded)
Desired Behavior
Allow configuration of the default limit via:
- Environment variable (e.g.,
SUPERMEMORY_RECALL_LIMIT=20)
- Config option (e.g.,
recallCommandDefault: 20 in openclaw.json)
Use Case
For power users building complex projects, 5 memories often doesn't provide enough context coverage. The memories are already condensed (relevance-scored), so showing 10-20 gives much better "bang for buck" without significant token overhead.
Our Temporary Patch
We needed this working now, so we patched it locally. Here's what we changed for anyone who needs this immediately:
File: commands/slash.ts (line 52)
// Before (hardcoded):
const results = await client.search(query, 5)
// After (uses config):
const results = await client.search(query, _cfg.maxRecallResults)
Config in openclaw.json:
{
"plugins": {
"entries": {
"clawdbot-supermemory": {
"config": {
"maxRecallResults": 20,
...
}
}
}
}
}
Note: After editing, clear Bun's cache and restart:
rm -rf ~/.bun/install/cache
# Restart OpenClaw gateway
Suggested Implementation
Add a new config option recallCommandDefault that falls back to maxRecallResults if not set:
// In commands/slash.ts
const limit = _cfg.recallCommandDefault ?? _cfg.maxRecallResults ?? 5
const results = await client.search(query, limit)
Or support an environment variable for Docker/container deployments:
SUPERMEMORY_RECALL_DEFAULT=20
Workaround (No Patch)
Users can currently use:
/recall <query> --limit 20
But this is easy to forget and not discoverable for new users.
Environment
- OpenClaw: 2026.1.29
- Plugin: clawdbot-supermemory
- Runtime: Bun
Happy to test or help document this! The plugin is awesome — this would make it even more flexible for power users. 🚀
Related: The maxRecallResults config option works great for auto-recall into AI context — just need the same flexibility for manual /recall commands.
Feature Request: Configurable Default Limit for
/recallCommandProblem
The
/recallslash command currently has a hardcoded default of 5 memories, which feels limiting for users with dense conversation history. WhilemaxRecallResultscontrols auto-recall into AI context, the CLI/recallcommand ignores this setting.Current Behavior
/recall working with jenny # Returns: 5 memories (hardcoded)Desired Behavior
Allow configuration of the default limit via:
SUPERMEMORY_RECALL_LIMIT=20)recallCommandDefault: 20inopenclaw.json)Use Case
For power users building complex projects, 5 memories often doesn't provide enough context coverage. The memories are already condensed (relevance-scored), so showing 10-20 gives much better "bang for buck" without significant token overhead.
Our Temporary Patch
We needed this working now, so we patched it locally. Here's what we changed for anyone who needs this immediately:
File:
commands/slash.ts(line 52)Config in
openclaw.json:{ "plugins": { "entries": { "clawdbot-supermemory": { "config": { "maxRecallResults": 20, ... } } } } }Note: After editing, clear Bun's cache and restart:
Suggested Implementation
Add a new config option
recallCommandDefaultthat falls back tomaxRecallResultsif not set:Or support an environment variable for Docker/container deployments:
Workaround (No Patch)
Users can currently use:
But this is easy to forget and not discoverable for new users.
Environment
Happy to test or help document this! The plugin is awesome — this would make it even more flexible for power users. 🚀
Related: The
maxRecallResultsconfig option works great for auto-recall into AI context — just need the same flexibility for manual/recallcommands.