memwal_remember tool description conflicts with proactive-memory use cases

Open Beginner friendly
#381 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
ai, documentation

Research direction

Start by locating the memwal_remember MCP tool description and reviewing its explicit-request guardrail in the context of proactive-memory use cases. Done means the guidance no longer conflicts with proactive writes, either through softened wording or an explicit opt-in for agents that use them.

Written by the indexing model from the issue text.

Description

The memwal_remember MCP tool's description states "Call ONLY when the user explicitly asks to remember/save something." This directly conflicts with building any agent designed to write memory proactively based on its own judgment (e.g. on decisions, failures, or errors) rather than on explicit user request — which is a core, encouraged pattern for agent memory systems. Recommend softening this guardrail or documenting an explicit opt-in for proactive-write agents.

Dominant language
TypeScript
Stars
107
Forks
37
Avg merge
3d 2h
Merged PRs (30d)
101

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MystenLabs/MemWal

All issues in MystenLabs/MemWal

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.