Skip to main content
The Cognee — Project Memory extension gives your editor a persistent, citable memory of the project. Remember and recall knowledge without leaving VS Code, and ask your project memory — get answers grounded in what Cognee knows about the current repository, with links back to the exact source files. It works against a local Cognee server or, as covered here, your Cognee Cloud tenant. The extension needs no environment variables — it’s configured entirely through VS Code settings and secret storage.

​
1. Install the extension

Install Cognee — Project Memory (extension ID cognee.cognee-vscode) from the VS Code Marketplace — search for it in the Extensions view. If it isn’t available in your Marketplace yet, install the bundled VSIX with Install from VSIX…, or the CLI:
Requires VS Code 1.85.0 or newer.

​
2. Connect to Cognee Cloud

Run Cognee: Set Up from the command palette (Cmd/Ctrl + Shift + P):
1

Enter your endpoint

Your Cloud tenant URL, e.g. https://your-tenant.aws.cognee.ai.
2

Enter your API key

A key from the API Keys page. It’s stored securely in the OS keychain (secret storage) — not in settings.json.
3

Health check

The command runs a health check so you know the connection works before you start.

​
3. Use it

1

Remember

Open a file, select some code, and run Cognee: Remember Selection.
2

Ask

Run Cognee: Ask My Project Memory and ask a question — the answer appears in a panel with ranked, clickable citations that open the exact source file.

​
Commands

​
Per-repository datasets

Each repository maps to a stable vscode_<hash> dataset, derived from the git remote (or the workspace path as a fallback), so memory stays isolated per project. Set cognee.datasetOverride to pin a fixed dataset name instead.

​
Settings

​
How it works

The extension talks to Cognee over the HTTP API: Ask / Recall → POST /api/v1/recall (with include_references: true, scoped to the workspace dataset); Remember / Index → POST /api/v1/remember (ingest + graph build in one call); Forget → POST /api/v1/forget. Everything it ingests carries a Source: <path> header, so a citation resolves straight to the exact file — even when several files share a name.
Prefer GitHub Copilot’s agent mode instead of the extension? VS Code can also use Cognee as an MCP tool provider via .vscode/mcp.json — see Claude Desktop for the shared Cloud MCP config and Cloud MCP for the details.

GitHub Repository

Source, settings, and development guide

Cursor

Connect the Cursor editor via MCP