memory_list/memory_recall returns empty when called without explicit scope parameter

[huantian233]

Bug Description

memory_list and memory_recall tools return no results when called without an explicit scope parameter, even though memories exist in agent-specific scopes.

Steps to Reproduce

1. Store memories with scope agent:tg-dm-xxx (agent-specific scope)
2. Call memory_list without any scope parameter
3. Result: "No memories found" even though entries exist

Root Cause

In src/scopes.ts, the getAllScopes() method only returns explicitly defined scopes from this.config.definitions:

getAllScopes(): string[] {
  return Object.keys(this.config.definitions);
}

When memory_list is called without a scope parameter, it falls back to:

let scopeFilter = context.scopeManager.getAccessibleScopes(agentId);

For an agent with no explicit agentAccess entry and agentId = undefined, getAccessibleScopes(undefined) calls getAllScopes() which only returns [global], missing all agent:xxx scopes.

The issue is that built-in dynamic scope patterns like agent:${agentId} are not included in getAllScopes() even though getAccessibleScopes(agentId) would return them correctly for a known agentId.

Expected Behavior

Calling memory_list or memory_recall without a scope parameter should return memories from all accessible scopes including agent-specific scopes.

Suggested Fix

One approach: modify getAllScopes() to also include the agent pattern scopes:

getAllScopes(): string[] {
  const defined = Object.keys(this.config.definitions);
  const agentScopes = Object.keys(this.config.agentAccess).map(id => `agent:${id}`);
  return [...new Set([...defined, ...agentScopes])];
}

Or alternatively, fix the fallback logic in memory_list to handle the case where no agentId is resolved.

[AliceLJY]

Hi @huantian233, thanks for the thorough analysis!

This is actually two issues layered together:

1. agentId resolution bug (fixed on master)

When agentId is undefined at runtime, getAccessibleScopes(undefined) falls back to getAllScopes() which only returns explicitly defined scopes — missing dynamic agent:xxx scopes. This has been fixed in PR #270 (merged to master, not yet released). After the fix, agentId correctly resolves from the runtime context instead of being undefined.

2. Multi-agent scope isolation (by design)

Even with proper agentId resolution, an agent with id "main" will only see ["global", "agent:main", "reflection:main"] — it won't see agent:tg-dm-xxx memories. This is intentional — scope isolation prevents cross-agent data leakage.

For your Telegram multi-agent setup, the recommended approaches:

• Pass scope explicitly: memory_list(scope: "agent:tg-dm-xxx")
• Configure agentAccess in your plugin config to grant specific agents access to other scopes:

  "scopes": {
    "agentAccess": {
      "main": ["global", "agent:main", "agent:tg-dm-xxx"]
    }
  }

Why not change getAllScopes()?

Your suggested fix to include all agent pattern scopes in getAllScopes() would break the isolation model — an undefined/unresolved agent would suddenly see all agents' private memories. The safer path is proper agentId resolution (which PR #270 addresses).

The fix will be available in the next beta release. Hope this helps!

[AliceLJY]

与 #288 / #231 同根因：getScopeFilter 对 undefined agentId 的处理逻辑已在 v1.1.0-beta.10 修复（commit 699b0f2）。

升级到 beta.10 后，不传 scope 参数时 memory_list / memory_recall 应该能正常返回结果。如果升级后仍有问题请重新开 issue 🙏