Your personal memory, across sessions, agents, and devices.

Personal memory connected

Your Personal Memory,
Across |

Your agents forget context between sessions. memU gives every agent you use one shared, inspectable memory layer with source-linked recall.

Paste into agents
CodexClaudeCursorOpenClawHermesWorkBuddy
Login to copy

Fetch https://memu.so/SKILL.md by using API Key xxx as a Bearer token in the Authorization header. Then follow the retrieved instructions to install and configure memU, using the same key wherever required.

Codex· MacBook Proyesterday · 09:12live
[SES]
Claude Code· office desktoptoday · 14:05another agent
waiting…
OpenClaw· home servertonight · 22:41another device
waiting…
3 sessions · 3 agents · 3 devices
~/personal-memory
connected

Project preferences

The durable constraints every agent should know before it starts.

Summary

  • Keep the existing memU visual language
  • Lead with personal memory across agents
  • Prefer concise, product-first explanations

Source

  • Original project conversation
  • Launch brief

Updated

  • Today

Related

  • launch-decisions.md
  • things-to-avoid.md

Launch decisions

Why the product story changed and what should stay consistent.

Decisions

  • Position memU as one personal memory layer
  • Show Codex, Claude, Cursor, OpenClaw, Hermes, and WorkBuddy
  • Replace repeated long prompts with small context packs
  • Keep every memory record inspectable

Source

  • Product launch brief
  • Website review

Related

  • project-preferences.md
  • tool-patterns.md

Coding habits

Patterns learned from code sessions and review history.

Habits

  • Read the repository before editing
  • Reuse existing components and local helpers
  • Run lint and focused tests after changes
  • Keep unrelated files untouched

Source

  • Codex sessions
  • Code review history

Related

  • tool-patterns.md

Tool patterns

How each agent should retrieve and use personal memory.

Before a task

  • Retrieve only records related to the current request
  • Prefer recent decisions over stale assumptions
  • Keep source links attached to the context pack

After a task

  • Memorize durable decisions and preferences
  • Skip temporary details and duplicated text

Related

  • coding-habits.md
  • things-to-avoid.md

Things to avoid

Repeated mistakes that should not follow the user into another agent.

Avoid

  • Asking for project background that is already in memory
  • Pasting full conversation histories into every prompt
  • Hiding where a remembered fact came from
  • Changing the established visual style without approval

Source

  • User feedback
  • Previous revisions

Related

  • project-preferences.md
  • launch-decisions.md
one personal memory
Across your agent stack

Connect memU to every agent

Supported agents
Codex
Claude
Cursor
OpenClaw
Hermes
WorkBuddy
# Paste into a new Codex session
Fetch https://memu.so/SKILL.md by using API Key xxx as a Bearer token in the Authorization header. Then follow the retrieved instructions to install and configure memU, using the same key wherever required.

# Codex can now retrieve
# project preferences, launch decisions,
# coding habits, and tool patterns
Applications

One memory, across the work your agents do

memU carries preferences, decisions, and learned skills across the agents and workflows you use.

For enterprise

Bring cross-agent memory into your environment

We work with design partners to customize memory, deploy it on the right infrastructure, and connect the agents their teams already use.

Custom Memory Systems

Shape memory scope, retrieval behavior, storage, and embedding choices around the way your teams and agents actually work.

Memory and skill design
Retrieval and storage configuration

Private Deployment

Choose managed cloud or a supported self-hosted pilot with customer-controlled storage and embedding infrastructure.

Cloud or self-hosted architecture
SQLite or Postgres + pgvector

Agent Memory Integration

Connect the agents your organization already approves through packaged host adapters or a scoped custom integration.

Existing and internal agents
Record and retrieval verification
Enterprise design partner

Start with a scoped enterprise pilot

Prove the deployment and integration path with your real agents and data boundaries before expanding across the organization.

Architecture and data-boundary review
One agreed deployment path
Initial agent memory integrations
Rollout runbook and support window
Discuss an enterprise pilotcontact@nevamind.ai
Approved agent stack
Your existing agents
CClCu+
memU host adapters
Record · retrieve · verify
connected
Managed Cloud
Shared across devices
Self-hosted Pilot
Customer-controlled store
User + agent scopeSource-linked memoryDoctor verified

Enterprise capabilities are delivered through scoped design-partner engagements. Deployment, integration, and support terms are agreed for each pilot.

Open community

Join the memU community

Meet the developers, contributors, and researchers building memory that can travel across agents.

Trade memory and agent integration patterns
Get implementation help from other builders
Shape the open memory ecosystem with us
Join Discord
community.network
connected
Every agent connected

Your Personal Memory,
Across Every Agent

Install memU once. Retrieve the right context in Codex, Claude, Gemini, OpenClaw, Hermes, and more.
Keep every memory inspectable and linked to its source.

One-click install
Cross-agent context
Source-linked memory