Skip to content

← All guides

Archive memory guide

This Cline guide is preserved for existing users. Memory is now supporting infrastructure under the production-action control product.

Current offersRisk Review

How to Add Persistent Memory to Cline

Cline is one of the most popular AI coding assistants for VS Code, but it loses context between sessions. The Novyx MCP Server gives Cline persistent memory — your assistant remembers your project architecture, coding conventions, and past decisions across every session.

The Problem

  • ✗ Cline forgets everything when you start a new task or close VS Code
  • ✗ Custom instructions are static — they do not evolve as your project grows
  • ✗ No way to search what Cline learned in past sessions
  • ✗ No rollback if Cline internalizes wrong assumptions about your codebase

The Solution: Novyx MCP Server

The Novyx MCP Server exposes memory tools to Cline via the Model Context Protocol. Cline can store architecture decisions, recall past context, preserve audit context, and recover supported state — all persisted across VS Code sessions.

Setup

1. Install the MCP server:

bash
pip install novyx-mcp

2. Add to your Cline MCP configuration:

json
{
  "mcpServers": {
    "novyx-memory": {
      "command": "python",
      "args": ["-m", "novyx_mcp"],
      "env": { "NOVYX_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Open Cline settings in VS Code, navigate to MCP Servers, and add the configuration above. You can also add it to .cline/mcp_settings.json in your project root.

What Cline Can Do With Memory

Remember project patterns

"This project uses the repository pattern with dependency injection." — stored permanently, recalled in every future task.

Recall debugging history

"What caused that flaky test last week?" — instant recall from past sessions with semantic search.

Track architecture decisions

"We use SQLite for local dev and Postgres in production." — Cline never suggests the wrong database again.

Recover bad assumptions

"Forget that I said we use REST — we migrated to GraphQL." — supported recovery with audit context.

MCP Tools Available

CategoryTools
Core Memoryremember, recall, forget, list_memories, memory_stats, rollback, audit, link_memories, add_triple, query_triples
Context Spacescreate_space, list_spaces, space_memories, update_space, delete_space, share_space
Replayreplay_timeline, replay_snapshot, replay_lifecycle, replay_diff
Experimental maintenanceOptional memory-maintenance helpers where enabled

See the full MCP server docs on the Integrations page.

Frequently Asked Questions

How do I add persistent memory to Cline?

Install novyx-mcp and configure it in your Cline MCP settings. Cline gains MCP memory tools so coding sessions can persist across restarts with semantic search and supported recovery workflows.

Does Cline support MCP servers?

Yes. Cline has native MCP support. You can add MCP servers through the Cline settings panel in VS Code under the MCP Servers section.

What is the difference between Cline custom instructions and Novyx memory?

Custom instructions are static text you write manually. Novyx memory is dynamic — the AI stores and retrieves context automatically. It includes semantic search, audit context, and supported recovery workflows that custom instructions cannot provide.

Start with the production-action gate

For the current product path, start with a governed production action.

Run the gate