-
-
Notifications
You must be signed in to change notification settings - Fork 79.2k
[Feature]: Per-agent memory-wiki vault configuration #63829
Copy link
Copy link
Open
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:needs-security-reviewClawSweeper marked this issue as needing security-sensitive review.ClawSweeper marked this issue as needing security-sensitive review.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.enhancementNew feature or requestNew feature or requestimpact:securitySecurity boundary, credential, authz, sandbox, or sensitive-data risk.Security boundary, credential, authz, sandbox, or sensitive-data risk.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Description
Metadata
Metadata
Assignees
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:needs-security-reviewClawSweeper marked this issue as needing security-sensitive review.ClawSweeper marked this issue as needing security-sensitive review.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.enhancementNew feature or requestNew feature or requestimpact:securitySecurity boundary, credential, authz, sandbox, or sensitive-data risk.Security boundary, credential, authz, sandbox, or sensitive-data risk.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Summary
Add per-agent memory-wiki vault configuration support, allowing each agent in a multi-agent setup to maintain its own isolated knowledge wiki instead of sharing a single global vault.
Problem to solve
Currently, the
memory-wikiplugin only supports global configuration viaplugins.entries["memory-wiki"]. This means all agents share a single wiki vault, which doesn't fit multi-agent scenarios where different agents have different knowledge domains.In a multi-agent setup (e.g., technical-expert for system ops, ai-engineer for ML development), each agent has different knowledge domains, different memory content, and different wiki pages. Currently, enabling memory-wiki would merge all agents' knowledge into one wiki, causing search results mixing unrelated domains and difficulty maintaining clean knowledge boundaries.
Proposed solution
Add support for per-agent memory-wiki vault configuration.
Option 1: Agent-level plugin config
Allow
agents.list[].plugins.entries["memory-wiki"]to override global config, so each agent can have its own vault path.Option 2: New vault mode "per-agent"
Add a new
vaultMode: "per-agent"that creates a separate wiki vault for each agent, with path relative to agent workspace.Both approaches would allow isolated knowledge domains per agent while maintaining the existing global wiki behavior for single-agent setups.
Alternatives considered
Use
unsafe-localmode withpaths[]array - but this still shares a single index across all agents, mixing search results.Disable memory-wiki and manually read wiki files - loses semantic search capabilities.
Create separate OpenClaw installations per agent - adds operational complexity and resource overhead.
None of these provide clean per-agent knowledge isolation with semantic search.
Impact
Evidence/examples
No response
Additional information
Related source files:
dist/agent-scope-BoZcgjP9.js- agent config resolution (no plugins field)docs/plugins/memory-wiki.md- current vault modesdocs/reference/memory-config.md- memory configurationdocs/concepts/multi-agent.md- multi-agent architectureCurrent agent config includes
memorySearchper-agent override, butpluginsis not included. This creates an inconsistency where memory search can be configured per-agent, but the memory-wiki plugin cannot.