Use cases

On this page you will see how MMW is used in practice and can pick the scenario closest to yours. Every scenario relies only on features that already work.

1. One developer, several assistants

The situation. Anna writes the backend in Claude Code and edits the frontend in Cursor. In the morning, in Claude Code, she found out that tests must run with --forked, otherwise the database fixture fails. In the afternoon Cursor knows nothing about it.

With MMW.

• Both clients are connected to MMW with the same key (or keys of the same project); see Claude Code and Cursor.
• In Claude Code Anna says: “Remember in MMW: run integration tests with —forked, otherwise the database fixture fails. Fact key: tests-run.”
• In Cursor, before running tests, the agent calls search and finds the record with the unverified status and a date.

How do we run integration tests? Check MMW.

Expected answer: “MMW has a record: integration tests run with --forked, otherwise the database fixture fails (key tests-run).”

What else helps. Separate workspaces for separate projects (workspace="shop-backend") keep facts from mixing. If you turn on session history, Claude Code and Codex sessions are uploaded, but search over them is not available yet.

2. Team decisions

The situation. A six-person team decided: “New services use PostgreSQL 16; we don’t use MongoDB.” A month later a newcomer’s agent suggests MongoDB.

With MMW.

• The company sets up an organization; members accept invitations and issue their own keys.
• The decision is saved with fact_key="db-choice" and Unit visibility, so everyone in the unit and managers higher up the tree can see it.
• If someone later saves a different decision under the same key, the records with that key get the conflict status, and the agent shows the discrepancy instead of quietly picking one.

Tip

Agree on fact keys for important topics (db-choice, deploy-staging, code-style). New versions of decisions and conflicts are then detected automatically. See Best practices.

3. Support knowledge

The situation. The support team keeps hitting the same issue: after a password change a customer cannot sign in to the mobile app until they reinstall it.

With MMW.

• The agent saves the fix together with its source, a knowledge base article: source_id="kb/mobile-login" and source_hash set to the hash of the current article version.
• The next support agent asks their assistant and gets the fix with a reference to the article.
• When the article is rewritten, the agent calls validate_memory with the new hash: old records become stale, and nobody recommends an outdated workaround.

4. Offboarding without losing knowledge

The situation. Igor is leaving the infrastructure unit. His memory holds dozens of records about how networking and deployment work, some of them drafts visible to the author only.

With MMW.

1. His manager clicks Offboard and picks a knowledge recipient, Maria.
2. Igor’s keys are revoked immediately.
3. Maria sees all his records, drafts included, in the account and through her agent, and opens the useful ones to the unit.
4. Every read of handed-over knowledge and every visibility change goes to the organization audit log, without record content.

While Igor was working, his manager could not see his drafts. More in Offboarding and knowledge handover.

5. Personal notes from Telegram

The situation. You are in a meeting without a laptop and need to remember: “Supplier Alpha gives 7% off if paid before the 15th.”

With MMW.

• Send the note to the @mmwhub_bot bot; it saves it with the source telegram.
• A colleague’s message forwarded to the bot is saved together with its author.
• In the evening you ask Claude: “What are supplier Alpha’s terms?” and the assistant finds the same record. Or ask the bot directly, “What discount does Alpha give?”, and it answers from the matching records with date and source.

What these scenarios do not include

• MMW does not read your chats, email or repositories on its own: memory contains only what an assistant or you saved.
• There is no search over uploaded session history yet.
• There is no SSO, no automatic invitation emails and no import of employees from external directories: an invitation is a one-time link the admin passes on.

What’s next

Quickstart Connect and save your first fact.

Why MMW Compared with built-in memory, notes files and your own vector database.

Organizations Shared company memory with roles and visibility.

What to remember Rules that keep memory useful instead of noisy.