Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Wrong Binary Path Used during Installation

Aperta
  • Qualcosa non va?
#2,722 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
bash
Ambito
cli, developer-experience

Direzione di ricerca

Start at the codebase-memory-mcp install command and trace how it detects externally managed binaries and passes the selected path into generated MCP and plugin configuration. Check the install tests for mise-managed binaries and add coverage for this reproduction. Done when generated definitions use the detected mise path instead of $HOME/.local/bin/codebase-memory-mcp.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug editor/integration ux/behavior
Version

codebase-memory-mcp 0.12.1

Platform

macOS (Apple Silicon)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

ui

What happened, and what did you expect?

When using codebase-memory-mcp install it correctly detects cbm to be managed externally by mise (including the correct path) according to the logs:

❯ codebase-memory-mcp install
codebase-memory-mcp install 0.12.1

Binary is managed elsewhere by mise:
  $HOME/.local/share/mise/installs/github-deus-data-codebase-memory-mcp/latest/codebase-memory-mcp
Leaving it and your PATH untouched; configuring agents only.
  (use --force-binary to install a copy into $HOME/.local/bin anyway)

But it will still use $HOME/.local/bin/codebase-memory-mcp in all mcp & plugin files afterwards, which is wrong and does not exist.

Related to:

Reproduction
  1. Install cbm using e.g. mise
  2. Run codebase-memory-mcp install
  3. Check one of the generated mcp definitions
  4. Notice it used $HOME/.local/bin/codebase-memory-mcp instead of $HOME/.local/share/mise/installs/github-deus-data-codebase-memory-mcp/latest/codebase-memory-mcp
Logs
❯ codebase-memory-mcp install
codebase-memory-mcp install 0.12.1

Binary is managed elsewhere by mise:
  $HOME/.local/share/mise/installs/github-deus-data-codebase-memory-mcp/latest/codebase-memory-mcp
Leaving it and your PATH untouched; configuring agents only.
  (use --force-binary to install a copy into $HOME/.local/bin anyway)

Found XX existing index(es). Keeping them. After install, re-index to pick up this version's improvements:
  [...]

No CBM session needs to stop for install: the published binary and indexes are unchanged.
Detected agents: OpenCode VS-Code Junie Copilot-CLI

OpenCode:
  mcp: $HOME/.config/opencode/opencode.jsonc
  instructions: $HOME/.config/opencode/AGENTS.md
  skill: $HOME/.config/opencode/skills/codebase-memory/SKILL.md (0 installed)
  agent: $HOME/.config/opencode/agents/codebase-memory-scout.md
  agent: $HOME/.config/opencode/agents/codebase-memory.md
  agent: $HOME/.config/opencode/agents/codebase-memory-auditor.md
  extension: $HOME/.config/opencode/plugins/cbm-augment.ts
VS Code:
  mcp: $HOME/Library/Application Support/Code/User/mcp.json
VS Code:
  mcp: $HOME/Library/Application Support/Code/User/profiles/builtin/mcp.json
Junie:
  mcp: $HOME/.junie/mcp/mcp.json
  skill: $HOME/.junie/skills/codebase-memory/SKILL.md (0 installed)
  agent: $HOME/.junie/agents/codebase-memory-scout.md
  agent: $HOME/.junie/agents/codebase-memory.md
  agent: $HOME/.junie/agents/codebase-memory-auditor.md
Copilot CLI:
  mcp: $HOME/.copilot/mcp-config.json
  instructions: $HOME/.copilot/copilot-instructions.md
  skill: $HOME/.copilot/skills/codebase-memory/SKILL.md (0 installed)
  agent: $HOME/.copilot/agents/codebase-memory-scout.agent.md
  agent: $HOME/.copilot/agents/codebase-memory.agent.md
  agent: $HOME/.copilot/agents/codebase-memory-auditor.agent.md
  hooks: SessionStart + SubagentStart (dynamic graph context)

Install complete. Please restart your coding-agent sessions to properly take this into account.
Restart your shell or run:
  source $HOME/.zshrc
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.
Lingua principale
C
Stelle
45.8k
Fork
3.8k
Merge medio
3g 6h
PR unite (30g)
201

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DeusData/codebase-memory-mcp

Tutte le issue di DeusData/codebase-memory-mcp

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.