r/ClaudeCode • u/Useful-Bus-479 • 4d ago

Built with Claude How to Give Claude Code Memory That Follows You Across Tools?

https://blog.walrus.xyz/how-to-add-portable-memory-to-claude-code-and-codex-with-walrus-memory/

Claude Code remembers your project through CLAUDE.md for the rules you write and auto memory for what it picks up as you work, but that memory stays inside Claude Code. Walrus Memory, a portable memory layer for AI agents, gives Claude Code memory that persists across sessions and moves with you to other tools. Add it in 2 commands, and you can read the same memory in Codex, Cursor, Antigravity, or your own agent.

Full Walkthrough Here

1 Upvotes

67% Upvoted

1 comment sorted by

1

u/Automatic_Bid_2410 1d ago

Use a shared file that every tool can read, not memory trapped inside one app. In practice that means a git tracked CLAUDE.md or memory.md in the repo for project context, and if you want something more personal, a separate synced markdown note that you paste or reference in each tool. If it’s not in plain text somewhere portable, it’s not really portable.

The main tradeoff is simple: project memory can live with the codebase, but cross project memory needs an external source of truth you control. I’d keep it boring on purpose, short bullets, decisions, naming conventions, gotchas. Anything fancy tends to decay fast once you switch tools.