VS Code extension (v0)

Sidebar memory browser, save-selection shortcut, recall palette.

A separate VS Code extension lives at sdks/vscode/ in the mnueron repo. It works alongside any AI plugin you already use (Copilot, Cursor, Cline, Continue) — mnueron is the memory, not the AI.

What you get

  • Sidebar memory list in the activity bar. Shows your 25 most recent memories in the active namespace.
  • Save selectionCmd+Shift+M (mac) / Ctrl+Shift+M (win). Saves the current editor selection as a memory tagged with the file language.
  • RecallCmd+Shift+R / Ctrl+Shift+R. QuickPick search; picking a result inserts it at the cursor (or copies to clipboard with no editor focused).
  • Namespace switcher in the status bar.
  • Ambient context (optional): when you open a file, mnueron quietly searches for related memories and shows a count in the status bar.

⚠️ Double-clicking the .vsix opens the WRONG app

On Windows, .vsix files are file-associated to Visual Studio Installer (the full Microsoft IDE) by default. That is not the same product as Visual Studio Code. If you double-click the file you'll get an error like:

One or more extensions are for Visual Studio Code. Try installing them in Visual Studio Code.

Don't double-click. Use one of the install paths below instead — either the one-line helper script, the code --install-extension CLI command, or VS Code's Cmd/Ctrl+Shift+P → "Extensions: Install from VSIX...".

IconAppUse for our extension?
Purple ribbon, "Visual Studio 2022"Visual Studio (Microsoft IDE)❌ NO
Dark blue infinity, "Visual Studio Code" or "Code"VS Code (the editor)✅ YES

Until we publish to the VS Code Marketplace, the cleanest install is a single helper script that handles npm install, build, package, and VS Code install for you.

Windows (PowerShell):

cd C:\Mnueron\Mnueron\mnueron-v0.1.0\mnueron\sdks\vscode
./install.ps1

mac / linux:

cd /path/to/mnueron/sdks/vscode
./install.sh

The script verifies you have Node 18+, npm, and the code CLI on your PATH, then runs the full build-and-install in about 30 seconds. After it finishes, reload your VS Code window (Cmd/Ctrl+Shift+P → "Developer: Reload Window") and the mnueron icon appears in the activity bar.

What the script does, exactly

  1. Verifies node, npm, and code (the VS Code CLI) are all on PATH.
  2. Runs npm install to fetch typescript + @types/vscode + @types/node.
  3. Installs @vscode/vsce globally if it's not already there.
  4. Compiles TypeScript via npm run build.
  5. Packages the result into mnueron-vscode-X.Y.Z.vsix.
  6. Installs the VSIX into VS Code via code --install-extension.
  7. Prints the post-install checklist.

If anything fails, the script halts with a clear error pointing at the missing prerequisite.

If the code command isn't on PATH

That's the most common first-time stumble. Fix:

  1. Open VS Code.
  2. Cmd+Shift+P / Ctrl+Shift+P → type "Shell Command: Install 'code' command in PATH".
  3. Confirm. Restart your terminal.
  4. Verify: code --version should print VS Code's version.

Install — manual steps

If you want full control (or install.ps1 doesn't fit your setup), here are the exact commands:

# 1. Get the deps
cd C:\Mnueron\Mnueron\mnueron-v0.1.0\mnueron\sdks\vscode
npm install
npm install -g @vscode/vsce

# 2. Build + package
npm run build
vsce package --no-dependencies --skip-license

# 3. Install the .vsix in VS Code
code --install-extension mnueron-vscode-0.1.0.vsix --force
# OR via the UI:
#   Cmd/Ctrl+Shift+P -> "Extensions: Install from VSIX..." -> pick the file

First-run configuration

After install, open VS Code Settings (Cmd/Ctrl+,) → search "mnueron":

SettingDefaultWhat to set
mnueron.modelocallocal talks to the CLI's dashboard server. hosted talks to mnueron.com.
mnueron.hostedUrlhttps://www.mnueron.comOverride for self-hosting.
mnueron.localUrlhttp://127.0.0.1:3122Local CLI dashboard URL.
mnueron.apiToken""Bearer token (mnu_...) for hosted mode. Issue one at /account-settings/tokens.
mnueron.activeNamespacevscodeNamespace used when you save from this editor.
mnueron.ambientContextfalseSearch for related memories when opening files.

Local mode prerequisites

The extension talks to 127.0.0.1:3122. Start the local dashboard server in any terminal before using the extension:

mnueron dashboard

That stays running and the extension's reads / writes flow through it into ~/.mnueron/memories.db.

Hosted mode prerequisites

You need a mnueron.com account and a bearer token. Paste the token into mnueron.apiToken. No local server needed — the extension talks directly to mnueron.com.

Verify it works

  1. Sidebar shows up — click the mnueron icon in the activity bar. You should see "No memories in this namespace yet" the first time, or your recent memories if you have any.
  2. Save a selection — open any file, select a few lines, press Cmd/Ctrl+Shift+M. Toast: "Saved to vscode (xxxxxxxx)". The sidebar refreshes with the new memory.
  3. Recall it — press Cmd/Ctrl+Shift+R, type a word from what you saved, hit Enter. The memory text is inserted at the cursor.

See Testing the VS Code extension for the full diagnostic recipe if any step fails.

Why complementary to Cline / Cursor / Continue

If you already use Cline, Cursor, or Continue, their AI already has mnueron via MCP (configured by mnueron setup). The VS Code extension adds UI surface: a sidebar to browse, shortcuts to save explicitly, recall-and-paste into any prompt.

If you use GitHub Copilot, which doesn't speak MCP, this extension is how Copilot users get mnueron. Recall + copy + paste into Copilot's chat panel as context.

Coming next

  • VS Code Marketplace listing — the one-click install path. Pending dogfooding period.
  • Auto-capture commit messages as memories tagged by repo.
  • CodeLens ("you wrote 3 memories about this file last month").
  • Remote dev container support so the extension works in Codespaces.

Track progress: https://github.com/randi2160/mnueron/issues.

Last updated 2026-05-19edit