Multiple codebase memory .exe running

[testsubject8383]

Version

codebase-memory-mcp 0.10.8

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

Run OpenCode, even without doing anything in it, just starting it. There are multiple (5-6) codebase memory executables running at the same time, each taking a few % of CPU.

This happens in OC CLI, in Desktop App and in the alternative OpenChamber GUI app.

I found this, tl/dr: "resolved multiple instances", but I'm seeing multiple instances without even doing anything in OC:

#50

Reproduction

Run OC with the Codebase MCP. That's it.

Logs

Diagnostics trajectory (memory / performance / leak issues)

Project scale (if relevant)

No response

Confirmations

• I searched existing issues and this is not a duplicate.
• My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

[DeusData]

Thanks for reporting this and checking several OpenCode interfaces. Several executable entries can represent different roles, including MCP connection processes, the shared daemon, and indexing workers. We still need to identify which roles your five or six processes have.

I found repeated idle maintenance checks in v0.10.8, and v0.11.0 contains changes that reduce that work. That is a possible explanation for the CPU usage, but we have not confirmed it in your case.

With just one affected application open, please share its name/version and, after leaving it untouched for about a minute:

• The process list from the command below, plus which PIDs still use CPU and roughly how much.
• codebase-memory-mcp daemon status, using the same executable configured for that application.
• Which processes remain after closing the application, and for approximately how long.

Get-CimInstance Win32_Process -Filter "Name LIKE '%codebase-memory%'" |
  Select-Object ProcessId, ParentProcessId, ExecutablePath, CommandLine |
  Format-List

Please redact private paths, arguments, and any credentials. If you are still using v0.10.8, a comparison with v0.11.0 in that same application would also help: please report whether CPU usage changes and whether the process count changes separately. Thank you!

[github-actions]

Thanks for the report! To move this forward we need a bit more so we can reproduce it ourselves:

• the codebase-memory-mcp --version you're on
• the exact steps or command you ran
• a public repo (or a small dummy snippet) that shows the problem — please don't paste proprietary code

Once that's here we'll pick it straight back up. Heads-up: issues left awaiting-reporter are automatically closed after a few weeks of silence, but a comment reopens the door anytime.