README

   
  
     
  



  🇨🇳 中文 •
  🇹🇼 繁體中文 •
  🇯🇵 日本語 •
  🇵🇹 Português •
  🇧🇷 Português •
  🇰🇷 한국어 •
  🇪🇸 Español •
  🇩🇪 Deutsch •
  🇫🇷 Français •
  🇮🇱 עברית •
  🇸🇦 العربية •
  🇷🇺 Русский •
  🇵🇱 Polski •
  🇨🇿 Čeština •
  🇳🇱 Nederlands •
  🇹🇷 Türkçe •
  🇺🇦 Українська •
  🇻🇳 Tiếng Việt •
  🇵🇭 Tagalog •
  🇮🇩 Indonesia •
  🇹🇭 ไทย •
  🇮🇳 हिन्दी •
  🇧🇩 বাংলা •
  🇵🇰 اردو •
  🇷🇴 Română •
  🇸🇪 Svenska •
  🇮🇹 Italiano •
  🇬🇷 Ελληνικά •
  🇭🇺 Magyar •
  🇫🇮 Suomi •
  🇩🇰 Dansk •
  🇳🇴 Norsk


Your coding agent forgets everything between sessions. Claude-Mem remembers for it.


  
    
  
  
    
  
  
    
  
  
    
  



 
   
 





  
    
      
        
          
        
      
    
    
      
        
          
          
          
        
      
    
  



  Quick Start •
  How It Works •
  Search Tools •
  Documentation •
  Configuration •
  Troubleshooting •
  License



  Every new session, your agent starts from zero. It re-reads the same files, re-asks the same questions, and walks back into mistakes you already fixed together.



  Claude-Mem runs a second agent beside it that takes notes while it works. The next session starts with a short index of what matters, and pulls in the details only when it needs them. Works with Claude Code, Codex, Cursor, OpenCode and 11 more agents. Copilot CLI, Goose, Roo Code and Warp can search your memory, but their sessions aren't recorded.


---

 Quick Start

Installing for someone as an AI agent? Run npx claude-mem install --runtime worker on their computer in an interactive terminal (enable PTY in your shell tool). It first asks in the terminal which agents to set up and, for Claude Code, whether to disable native auto-memory (and whether to overwrite an existing install). Relay each question to the user and type their answer, or pass --ide  to skip the first one. Keep the installer running. When it prints Continue setup in your browser, open that URL in the user's browser if the installer hasn't already opened it. Let the user go through setup and make their own choices, including the usage-analytics question the installer may ask at the end. If you can't run an interactive terminal on their computer, give them the command to run locally.

bash
npx claude-mem install


The installer finds the agents on your machine and asks which ones to set up. Then just start working: observations stream in from your first prompt, and your second session in a project opens with memory from the first. (Copilot CLI, Goose, Roo Code and Warp get memory search only, so their sessions don't add to it.)

The installer sets everything up first, then asks you to sign in to claude-mem in your browser (email magic link, no card required to sign in). Choosing the claude-mem observer then starts its 30 Day Free Trial on a checkout page that asks for a payment method; once it completes, the installer saves your memory key. With the observer, memory runs off-plan, so you get up to 100% more usage from you

Top issues

Discussions

Latest release

Images are kept by default and show in My Work

- Kept by default: screenshots and images your agent reads or makes are now kept and linked to the observations from that turn, without sending them to an AI model. Image inference stays off (5426).
- "Keep images" switch: the memory viewer's Settings has a new Images section. Turning Keep images off stops keeping new images; images already kept stay. A "false" you saved yourself is respected (5426).
- Gallery in My Work: request cards show an image count and the first four thumbnails; the request drawer shows every linked image; any thumbnail op