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?
Summary
The installer successfully downloads, verifies, extracts, and installs the CBM binary, but fails during automatic agent configuration.
The same install run reports failures for:
- Claude Code —
mcp_install
- Claude Code —
hook_register
- Codex CLI —
hook_preflight, reason=command_render
- Gemini CLI —
instructions_install
- VS Code —
mcp_install
The binary is kept, but installation exits with code 1.
Relevant output
Installed binary -> %LOCALAPPDATA%/Programs/codebase-memory-mcp/codebase-memory-mcp.exe
Claude Code:
error: agent_config agent=Claude Code op=mcp_install path=%USERPROFILE%/.claude.json (target: regular file, 5430 bytes)
error: agent_config agent=Claude Code op=hook_register path=%USERPROFILE%/.claude/settings.json (target: regular file, 10147 bytes)
Codex CLI:
error: agent_config agent=Codex CLI op=hook_preflight path=%USERPROFILE%/.codex/config.toml reason=command_render (target: regular file, 12768 bytes)
Gemini CLI:
error: agent_config agent=Gemini CLI op=instructions_install path=%USERPROFILE%/.gemini/GEMINI.md (target: regular file, 11513 bytes)
VS Code:
error: agent_config agent=VS Code op=mcp_install path=%APPDATA%/Code/User/mcp.json (target: regular file, 192 bytes)
error: one or more agent configurations failed
error: activation stopped after one or more agent configuration or cleanup operations failed
error: installation failed (exit code 1)
Expected behavior
The installer should either:
- update valid existing agent configs successfully, or
- report the actual parse/render/write error for each failed config operation.
(target: regular file, N bytes) does not currently explain why the operation failed.
It would also be useful if failure of one optional agent integration did not abort activation for all others.
Notes
Other detected integrations configure successfully during the same run, so the CBM binary itself appears to install correctly.
The failures span JSON, TOML, and Markdown files, so this may be broader than a single config parser issue.
Related issues:
I opened this separately because this case affects multiple agent integrations in the same install run. If the root cause is identical, feel free to close as duplicate.
Workaround
.\install.ps1 --skip-config
then configure the required MCP clients manually.
Reproduction
Reproduction
with existing configs for Claude Code, Codex CLI, Gemini CLI, and VS Code.
Logs
Diagnostics trajectory (memory / performance / leak issues)
Project scale (if relevant)
No response
Confirmations
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?
Summary
The installer successfully downloads, verifies, extracts, and installs the CBM binary, but fails during automatic agent configuration.
The same install run reports failures for:
mcp_installhook_registerhook_preflight,reason=command_renderinstructions_installmcp_installThe binary is kept, but installation exits with code
1.Relevant output
Expected behavior
The installer should either:
(target: regular file, N bytes)does not currently explain why the operation failed.It would also be useful if failure of one optional agent integration did not abort activation for all others.
Notes
Other detected integrations configure successfully during the same run, so the CBM binary itself appears to install correctly.
The failures span JSON, TOML, and Markdown files, so this may be broader than a single config parser issue.
Related issues:
I opened this separately because this case affects multiple agent integrations in the same install run. If the root cause is identical, feel free to close as duplicate.
Workaround
then configure the required MCP clients manually.
Reproduction
Reproduction
with existing configs for Claude Code, Codex CLI, Gemini CLI, and VS Code.
Logs
Diagnostics trajectory (memory / performance / leak issues)
Project scale (if relevant)
No response
Confirmations