Skip to content

feat: isolate MemOS memory by agent namespace#1623

Merged
hijzy merged 1 commit into
MemTensor:mem-agent-0424from
hijzy:dev
May 6, 2026
Merged

feat: isolate MemOS memory by agent namespace#1623
hijzy merged 1 commit into
MemTensor:mem-agent-0424from
hijzy:dev

Conversation

@hijzy
Copy link
Copy Markdown
Collaborator

@hijzy hijzy commented May 6, 2026

Summary

  • Add namespace ownership fields for Hermes profiles and OpenClaw agents across MemOS memory rows.
  • Thread runtime namespace context through Hermes/OpenClaw adapters, retrieval, tools, and viewer APIs.
  • Enforce private-vs-shared visibility while preserving local/public/hub sharing flows.

Test plan

  • npm run lint
  • npx vitest run tests/unit/pipeline/memory-core.test.ts tests/unit/storage/migrator.test.ts tests/unit/bridge/methods.test.ts tests/unit/adapters/hermes-protocol.test.ts tests/unit/adapters/openclaw-bridge.test.ts tests/unit/adapters/hermes-persistence.test.ts
  • /Users/jiang/MyProject/MemOS-jiang/.venv/bin/ruff check apps/memos-local-plugin/adapters/hermes/memos_provider
  • /Users/jiang/MyProject/MemOS-jiang/.venv/bin/ruff format --check apps/memos-local-plugin/adapters/hermes/memos_provider

Note: full npm run test:unit still has unrelated existing failures in reward.integration, reward.subscriber, and memory/l3/cluster.

Add namespace ownership to local memory rows so Hermes profiles and OpenClaw agents can keep private memory separate while still supporting explicit local and hub sharing.
@hijzy hijzy merged commit 68056a2 into MemTensor:mem-agent-0424 May 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant