Testing the VS Code extension

Use this after installing the extension via VSIX (see VS Code extension docs).

Pre-flight (1 minute)

1. Settings → mnueron. Set mnueron.mode to hosted or local.
2. If hosted: paste a bearer token from /account-settings/tokens into mnueron.apiToken.
3. If local: in a terminal, run mnueron dashboard so the local server is reachable at 127.0.0.1:3122.
4. Reload the VS Code window (Cmd+Shift+P → "Reload Window").

Test 1 — sidebar shows memories (30 sec)

1. Click the mnueron icon in the activity bar (far left).
2. The sidebar should list your 25 most recent memories in the configured namespace.

Pass: at least one memory appears; clicking opens it in a peek view.

Fail modes:

• "No memories in this namespace yet" → switch namespace via the status bar to one that has data, or save one first (Test 2).
• Sidebar empty + status bar shows mnueron • <namespace> → backend reachable but namespace is empty. Try the dashboard URL listed in settings to confirm what's actually there.
• Sidebar empty + no status bar entry → backend not reachable; check the URL in settings and your network.

Test 2 — save a selection (15 sec)

1. Open any file. Select a few lines (5-10 lines is fine).
2. Press Cmd+Shift+M (mac) / Ctrl+Shift+M (win).
3. A "Saved to <namespace>" toast appears, with a "Show in sidebar" button.

Pass: memory appears in the sidebar with the selected text as content, file path + language stored under metadata.

Fail modes:

• No toast → check the Output panel (View → Output → "mnueron") for an error. Most common: missing/invalid token in hosted mode.

Test 3 — recall and inject (30 sec)

1. Open any text file (or open a new untitled file).
2. Click somewhere in the file to place the cursor.
3. Press Cmd+Shift+R / Ctrl+Shift+R.
4. Type a few words from the memory you just saved.
5. Hit Enter on the matching result.

Pass: the memory's content is inserted at the cursor position.

Fail modes:

• No results → broaden the search; the QuickPick uses BM25 which needs at least one matching keyword.
• Stuck "Searching mnueron…" → backend unreachable; check Output panel.

Test 4 — namespace switching (15 sec)

1. Click the mnueron • <namespace> status bar entry (bottom right).
2. A QuickPick lists your namespaces with counts.
3. Pick a different namespace.

Pass: sidebar refreshes to show that namespace's memories.

Test 5 — ambient context (optional, opt-in)

1. Settings → enable mnueron.ambientContext.
2. Open a file.
3. After 1-2 seconds, the status bar shows mnueron • <ns> • N related if any memories match the filename or surrounding context.

Pass: "N related" count appears for files you've worked on before.

Test 6 — testing the OTHER IDE integrations (MCP path)

For Cursor, Claude Code, Cline, Continue, Windsurf, Zed, etc., mnueron isn't a VS Code-style extension — it's an MCP server wired via mnueron setup. Verify those integrations like this:

1. Open a chat in your AI tool.
2. Ask: "What MCP tools do you have available?"
3. The AI should list memory_save, memory_recall, memory_list, memory_get, memory_delete, memory_get_thread.
4. Save a test memory: "Remember that I prefer dark mode for everything."
5. Start a fresh chat in the same tool (or a different one).
6. Ask: "What did I tell you about my UI preferences?"
7. The AI should call memory_recall and respond with the dark-mode preference.

If step 3 fails (tools don't show up), the MCP server isn't connected:

• Confirm mnueron setup was run for that tool
• Restart the tool fully (quit + reopen, not just refresh)
• Check the config file the wizard wrote, e.g.:
  • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (mac) or %APPDATA%/Claude/claude_desktop_config.json (win)
  • Cursor: ~/.cursor/mcp.json
  • Cline: VS Code's extension settings

When to file an issue

Capture the Output panel content (View → Output → "mnueron" channel) and the contents of ~/.mnueron/last_capture.json if it exists, then open an issue at https://github.com/randi2160/mnueron/issues.