Use Case Guide · v1.7.2

VEKTOR for Claude Code & Cursor

Claude Code and Cursor forget everything the moment a session ends, gets compacted, or your machine reboots. VEKTOR gives them a persistent, local-first memory graph that survives all three — wired in through MCP in one command.

The problem

Every new session starts cold. The agent re-discovers your project's conventions, re-asks about architecture decisions you already made, and re-learns which approaches you already ruled out — burning tokens and your patience on the same ground, repeatedly. Context compaction makes it worse: anything not actively in the window is gone.

How VEKTOR solves it

VEKTOR runs as a local MCP server. Claude Code and Cursor call memory.recall() and memory.store() the same way they call any other tool — except what gets stored lives in a SQLite file on your machine, not in the conversation window, and survives indefinitely.

What gets remembered

Architectural decisions, coding conventions, why a given approach was rejected, in-progress task state, and bug-fix history — all auto-tagged and graph-wired via MAGMA so related memories surface together, not just keyword matches.

Setup

The setup wizard configures both editors in the same pass:

bash

vektor setup   # detects and configures Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, Continue

No manual MCP JSON editing required — the wizard writes the config, verifies the connection, and runs a smoke test automatically. Full steps in the Quickstart guide.

Example workflow

Day one

You tell Claude Code "we're using a repository pattern for data access, not direct ORM calls in handlers." It stores that as a high-importance memory, tagged to the project.

Three weeks later, new session

A different Claude Code session, same project. You ask it to add a new endpoint. It recalls the repository-pattern decision unprompted and follows it — no re-explaining.

Idle overnight

The REM dream cycle runs in the background, compressing the week's scattered fragments into consolidated insights — so recall stays fast even after months of daily use.

Default behaviour vs. VEKTOR

	Default Claude Code / Cursor	With VEKTOR
Across sessions	Nothing persists	Full memory graph persists
After context compaction	Compacted history lost	Memory unaffected — lives outside the window
Project conventions	Re-stated every session	Recalled automatically
Where data lives	n/a (not persisted)	Local SQLite file, yours forever
Cost	—	$0 embedding cost, $9/mo SDK

Multi-editor note

The memory graph is shared across editors configured on the same machine — a decision Claude Code stores is recallable from Cursor on the same project, since both point at the same local database.

Next steps

Run the Quickstart to get installed in under 5 minutes, or see pricing & plans to get a licence key.