Repository memory, inside your IDE

Close to the code. Connected to its history.

Bring indexed relationships, history and repository status into VS Code and Cursor. Inspect context beside a declaration, then open Mnemon when you need the wider picture.

01

Peek at callers without leaving the code

Select the Mnemon caller count above a supported declaration to open callers peek inside the editor. Inspect the returned source locations alongside the code you are reading, without switching to the full application.

Memory CodeLens offers callers peek, dependency and history actions, and ownership or hotspot context near supported declarations. Available actions depend on the language, settings and indexed data; some member actions open the containing type's dependencies.

Your language server keeps providing live editing intelligence. The companion adds repository memory, including earlier changes.

VS Code showing Mnemon caller, change, owner and dependency CodeLens above DaemonSingleInstance and TryAcquire
VS Code / Mnemon CodeLensProduct capture

VS Code / Mnemon CodeLens

VS Code showing Mnemon caller, change, owner and dependency CodeLens above DaemonSingleInstance and TryAcquire
Native VS Code callers peek showing the Program declaration alongside DaemonSingleInstance
VS Code / Callers peekProduct capture

VS Code / Callers peek

Native VS Code callers peek showing the Program declaration alongside DaemonSingleInstance

02

Know which revision you are looking at

The status bar shows whether Mnemon is connected, indexing, stale or offline. Markdown WIP and Commit Note indicators provide entry points into pending work and recorded explanations, without treating uncommitted previews as indexed history.

Mnemon status-bar tooltip in VS Code showing a connected daemon, a ready repository and matching indexed and Git HEAD revisions
VS Code / Connection and index freshnessProduct capture

VS Code / Connection and index freshness

Mnemon status-bar tooltip in VS Code showing a connected daemon, a ready repository and matching indexed and Git HEAD revisions

03

Follow a CodeLens change into its history

Select a Mnemon change or commit CodeLens to open the relevant history in Mnemon. In the browser view, inspect indexed member evolution, signature events and commit references in the context of the selected symbol. This is Mnemon's application view, not a native editor peek panel.

Reveal the current symbol or a repository citation in Mnemon. Continue into Explorer, dependencies or history without starting the investigation again from the repository root.

Mnemon member history showing TryAcquire added in commit 427397c, with Program caller context
Member history / TryAcquireProduct capture

Member history / TryAcquire

Mnemon member history showing TryAcquire added in commit 427397c, with Program caller context

04

Reach Mnemon's commands from the status bar

Select the companion's status-bar entry to open the Mnemon commands in your editor. Open the desktop app, Dashboard or Code Explorer; reveal a symbol or citation; refresh status or reindex the workspace repository.

The same command list provides daemon controls and MCP configuration actions. Keep these operations close to your development session, while completing any consent and trust steps required by your host.

VS Code command palette filtered to Mnemon, showing navigation, CodeLens, daemon and MCP configuration actions
VS Code / Mnemon commandsProduct capture

VS Code / Mnemon commands

VS Code command palette filtered to Mnemon, showing navigation, CodeLens, daemon and MCP configuration actions

05

VS Code and GitHub Copilot

Use the companion's editor features in VS Code. Opt-in MCP setup helps connect the same memory to GitHub Copilot, with trust and server-start steps handled by the host.

06

Cursor

Use the shared editor features in Cursor, with MCP setup tailored to Cursor's configuration format. Cursor Agent retains its own workflow and trust controls; VS Code-specific chat features are not implied.

07

Other MCP hosts

Claude Code and other compatible hosts can query the memory through MCP. That connection does not add the extension's CodeLens, status bar or editor commands.

08

Connect to your local Mnemon installation

Install Mnemon, then add the extension. It discovers the local daemon, offers a start command and helps configure MCP with your consent. Editor connectivity and agent connectivity are separate: complete the host's MCP setup before expecting agent queries to work.