Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Wrong Binary Path Used during Installation

Abierto
  • ¿Algo no está bien?
#2,722 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bash
Área
cli, developer-experience

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
C
Estrellas
45.8k
Forks
3.8k
Merge medio
3 d 4 h
PR fusionados (30 d)
208

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DeusData/codebase-memory-mcp

Todos los issues de DeusData/codebase-memory-mcp

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.