DEDUPED Hot AI repos. Real use cases. What people build. Get the Monday 5

How to give Claude Code, Codex or Cursor memory across sessions with OpenViking

Install the OpenViking memory plugin so your coding agent remembers preferences and past work.

Short answer: Have an OpenViking server running (self-hosted or the hosted service); then run curl -fsSL https://openviking.ai/install | bash and pick your tools and server when asked; use a user key, not a root key. All steps.

  • Top pick
  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor

Who it is forA developer tired of re-explaining project rules and preferences to their agent every session.

The problemCoding agents forget everything between sessions or store memory where you cannot see it.

The outcomeCross-session memory stored as files you can read, edit and search.

What you need first

  • uv and Python for a self-hosted server, or the hosted OpenViking Service
  • A model provider for the server (Volcengine, OpenAI, Codex OAuth, Kimi, GLM or local Ollama)
  • A user key for the memory plugin (a root key cannot read or write memories)

Steps

  1. Have an OpenViking server running (self-hosted or the hosted service)
  2. Run curl -fsSL https://openviking.ai/install | bash and pick your tools and server when asked
  3. Use a user key, not a root key
  4. Restart your agent as the installer instructs, then follow the onboarding guide

Prompt for your agent

Install the volcengine/OpenViking memory plugin for <Claude Code or Codex or Cursor> against my server at <address>, walk me through onboarding, and show me where my memories are stored.

Caveat.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for volcengine/OpenViking and "Give Claude Code, Codex or Cursor memory across sessions"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer