Skip to content

The install script failed to detect Hermes(Desktop) and OpenCode(Desktop) on Windows #1180

Closed

Description

@smzh369

Version

codebase-memory-mcp --0.9.0

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

The installation script not only failed to detect OpenCode Desktop and Hermes Desktop, but also mistakenly assumed that I had installed Claude Code. In fact I only have a .claude folder and didn't install the cli.
By the way the codebase-memory-mcp.exe was installed into two places: C:\Users\myuser\AppData\Local\Programs\codebase-memory-mcp\ and C:/Users/myuser/.local/bin/. Both location are added to path.

Reproduction

1.Follow the Quick Start step by step on Windows PowerShell

Logs

PS C:\Users\myuser> PowerShell -ExecutionPolicy Bypass -File .\install.ps1
codebase-memory-mcp installer (Windows)
  variant: standard
  arch:    amd64
  target:  C:\Users\myuser\AppData\Local\Programs\codebase-memory-mcp\codebase-memory-mcp.exe

Downloading codebase-memory-mcp-windows-amd64.zip...
Checksum verified.
Extracting...
Installed: codebase-memory-mcp 0.9.0

Configuring coding agents...

信息: 没有运行的带有指定标准的任务。
codebase-memory-mcp install 0.9.0

Installed binary -> C:/Users/myuser/.local/bin/codebase-memory-mcp.exe

Detected agents: Claude-Code

Claude Code:
  skills: 1 installed
  mcp: C:/Users/myuser/.claude/.mcp.json
  mcp: C:/Users/myuser/.claude.json
  hooks: PreToolUse (Grep/Glob search-graph augmenter, non-blocking)
  hooks: SessionStart (MCP usage reminder on startup/resume/clear/compact)
  hooks: SubagentStart (MCP usage reminder for subagents)

Added C:/Users/myuser/.local/bin to PATH in C:/Users/myuser/.profile

Install complete. Restart your shell or run:
  source C:/Users/myuser/.profile
Added C:\Users\myuser\AppData\Local\Programs\codebase-memory-mcp to user PATH

Done! Restart your terminal and coding agent to start using codebase-memory-mcp.
PS C:\Users\myuser>

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.

Activity

  1. added this to the 0.9.1-rc milestone on Jul 19, 2026
  2. added
    priority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.
    on Jul 19, 2026
  3. DeusData commented on Jul 19, 2026

    @DeusData
    Owner

    Thanks for including the full installer transcript. This is now high priority in 0.9.1-rc under #395. I am keeping it separate from #1167 because this report also covers Hermes detection, false Claude detection from directory presence, and duplicate binary/PATH installation.

  4. DeusData commented on Aug 14, 2026

    @DeusData
    Owner

    Thank you @smzh369 — the full installer transcript is what makes this actionable, and three separate defects are visible in it: neither desktop client detected, Claude Code claimed purely from the presence of a .claude folder when you never installed the CLI, and the binary landing in both %LOCALAPPDATA%\Programs\... and .local\bin with both on PATH.

    That last one is a trap in its own right — it is how people end up upgrading one copy and running the other, which shows up again in #1168. Nothing here has been waiting on you.

    Status honestly: still open, still not fixed. Tonight's v0.10.5 is being cut for the issues that make cbm impossible to operate, and an installer that reports agents you do not have while missing the ones you do belongs in that set. Sorry for the wasted setup time.

  5. DeusData commented on Sep 26, 2026

    @DeusData
    Owner

    Thank you, @smzh369! The full transcript showed three separate problems. The duplicate binary is fixed: since v0.10.0, install.ps1 passes its install directory through, so there's one copy and one PATH entry. Two things are still open and tracked here:

    • Claude Code is still detected from a bare .claude folder alone.
    • There's no detection yet for the Hermes and OpenCode desktop apps.
  6. DeusData commented on Oct 1, 2026

    @DeusData
    Owner

    Thank you @smzh369. Your transcript showed all three problems, and #2468 fixes each of them:

    • Hermes: on native Windows, Hermes (the CLI installer, the MSIX package and the Desktop app) keeps its home in %LOCALAPPDATA%\hermes, but cbm only looked in ~/.hermes. cbm now uses %LOCALAPPDATA%\hermes on Windows, falling back to an existing legacy ~/.hermes, both for detection and for where config.yaml goes.
    • OpenCode Desktop: it is now detected from the data folder its built-in server creates.
    • Claude Code: a bare .claude folder no longer counts as Claude Code. Detection now needs Claude Code's own .claude.json, its settings.json, or the claude CLI.

    A PATH longer than 4 KB can also hide installed CLIs; that is handled separately in PR #2381. Thanks again for the careful report!

  7. added a commit that references this issue on Oct 2, 2026
  8. added a commit that references this issue on Oct 4, 2026
  9. DeusData commented on Oct 4, 2026

    @DeusData
    Owner

    Thank you @smzh369. Your transcript showed all three problems, and #2468 fixes each of them:

    • Hermes: on native Windows, Hermes (the CLI installer, the MSIX package and the Desktop app) keeps its home in %LOCALAPPDATA%\hermes, but cbm only looked in ~/.hermes. cbm now uses %LOCALAPPDATA%\hermes on Windows, falling back to an existing legacy ~/.hermes, both for detection and for where config.yaml goes.
    • OpenCode Desktop: it is now detected from the data folder its built-in server creates.
    • Claude Code: a bare .claude folder no longer counts as Claude Code. Detection now needs Claude Code's own .claude.json, its settings.json, or the claude CLI.

    A PATH longer than 4 KB can also hide installed CLIs; that is handled separately in PR #2381. Thanks again for the careful report!

    Landed on main in b5649e9 (#2468); it ships with the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingeditor/integrationEditor compatibility and CLI integrationpriority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.windowsWindows-specific issues

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions