[Bug] memory_update still returns 'not found or access denied' for accessible agent:main memories on v1.1.0-beta.9

[i0ivi0i]

Summary

On memory-lancedb-pro@1.1.0-beta.9, memory_update still fails for an agent:main memory that was just created and is clearly accessible.

Observed behavior:

• memory_store succeeds
• memory_list can see the memory
• memory_recall can find the memory
• memory_forget can delete the same memory ID
• but memory_update returns: Memory <id>... not found or access denied.

So this does not look like a full plugin failure. It looks like the update path is still broken or inconsistent, likely around ID/scope/context resolution.

Environment

• Plugin: memory-lancedb-pro@1.1.0-beta.9
• OpenClaw: 2026.3.13
• OS: Windows 11
• Scope used: agent:main
• Current runtime confirms plugin is loaded and tools are exposed.

Reproduction

1. Store a memory:
   • memory_store(text="MEMORY_UPDATE_RETEST_20260320_2052", importance=0.53, category="fact", scope="agent:main")
2. Confirm it exists:
   • memory_list(limit=15, scope="agent:main", category="fact")
   • returned ID: 3fd0304d-3e9c-49ef-8873-6ffb16ebdb24
3. Try updating the exact same ID:
   • memory_update(memoryId="3fd0304d-3e9c-49ef-8873-6ffb16ebdb24", text="MEMORY_UPDATE_RETEST_20260320_2052_UPDATED", importance=0.54, category="fact", scope="agent:main")
4. Actual result:
   • Memory 3fd0304d... not found or access denied.
5. Then immediately try forgetting the same ID:
   • memory_forget(memoryId="3fd0304d-3e9c-49ef-8873-6ffb16ebdb24", scope="agent:main")
6. Forget succeeds.

Why this seems important

This suggests the problem is specifically in memory_update, not in general memory visibility/access:

• same memory can be listed
• same memory can be recalled
• same memory can be forgotten
• but same memory cannot be updated

Possibly related upstream work

I noticed these existing items seem related:

• memory_update rejects agent-scoped memories as outside accessible scopes #231 memory_update rejects agent-scoped memories as outside accessible scopes
• Bug: memory_forget fails with 'outside accessible scopes' even when agent should have access #266 memory_forget fails with 'outside accessible scopes' even when agent should have access
• fix: use resolveToolContext for scope resolution in forget/update/stats/list tools #258 fix: use resolveToolContext for scope resolution in forget/update/stats/list tools
• fix: use resolveToolContext in memory_forget and memory_update #270 fix: use resolveToolContext in memory_forget and memory_update

However, this issue is being observed still in beta.9 runtime behavior during live testing on Windows with agent:main scope.

Expected behavior

If a memory ID is valid enough to be listed/recalled/forgotten within the same scope/context, memory_update should also be able to update it.

Actual behavior

memory_update reports not found or access denied for a memory that is otherwise clearly accessible.

[AliceLJY]

Hi @i0ivi0i, thanks for the detailed reproduction — very helpful as always.

This is a known issue caused by incorrect agentId resolution in the memory_update (and memory_forget) code path. When context.agentId is undefined at runtime, getAccessibleScopes(undefined) falls back to only configured scopes (e.g. ['global']), missing agent:main.

This has been fixed in PR #270 (merged to master), which aligns memory_update and memory_forget with the same resolveToolContext() pattern used by memory_recall and memory_store. However, beta.9 was released before this fix was merged, so it's not included in your current version.

The fix will be available in the next beta release. In the meantime, if you build from master you can verify it's resolved.

Related: #231, #266

[AliceLJY]

Fixed in 699b0f2.

Root cause: isAccessible(scope, undefined) used bypass semantics (any valid scope → true), but getScopeFilter(undefined) only returned explicitly defined scopes (["global"]), excluding implicit scopes like agent:main. So memory_update rejected accessible memories while recall/forget worked fine.

What changed:

• getScopeFilter now returns undefined (full bypass) when agentId is missing, matching isAccessible's existing behavior
• memory_update now uses runtimeContext.scopeManager (consistent with recall/forget)

Note: beta.10's resolveRuntimeAgentId already ensures agentId defaults to "main" in normal operation, so most users on beta.10 won't hit this anymore. This fix is defensive — prevents the same bug from recurring if any future code path passes undefined agentId.

Please upgrade to the latest master and confirm the fix works for you.

[AliceLJY]

已在 v1.1.0-beta.10 修复（commit 699b0f2）。升级到 beta.10 后此问题不再复现。