DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to carry Claude Code project context into new sessions with Claude Mem

Install the Claude Code plugin so earlier session context appears automatically when you start a new session.

Credentials. Signing in through the installer provisions a memory key for your account, so review what the account and provider settings grant before you connect it.

Who it is forA developer working on the same codebase with Claude Code across many days, who keeps re-explaining past decisions at the start of each session.

The problemClaude Code sessions end and the agent forgets what was built, decided, and fixed in earlier sessions.

The outcomeNew Claude Code sessions open with summaries of prior work on the project, so the agent continues where the last session stopped.

What you need first

  • Node.js 20.0.0 or higher
  • Claude Code with plugin support, or a supported agent host such as OpenCode or T3 Code
  • A claude-mem sign-in or your own memory provider key, if you do not use the installer's local option
  • Bun and uv, which the README says are auto-installed if missing

Steps

  1. In Claude Code, run /plugin marketplace add thedotmack/claude-mem
  2. Run /plugin install claude-mem
  3. Restart Claude Code
  4. Start a new session in the same project and check that context from the previous session appears

Prompt for your agent

Install the claude-mem plugin in Claude Code for the repo at <project path> using `/plugin marketplace add thedotmack/claude-mem` and `/plugin install claude-mem`, then restart Claude Code. Report whether a new session in <project path> shows context from a previous session. Verify by checking that the injected context references work from the earlier session.

Caveat. The README says the npm package installs only the SDK, so the plugin must be installed through the /plugin commands or npx Claude Mem install.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page