V0.10 update / install fails

[iandol]

Update from previous version failed due to there not being a ui release variant (this is ok I suppose though you might want to mention it in release notes):

codebase-memory-mcp update
codebase-memory-mcp update (current: 0.9.0)

Update available: 0.9.0 -> v0.10.0
Which binary variant do you want?
  1) standard  — MCP server only
  2) ui        — MCP server + embedded graph visualization
Choose (1/2): 2

Downloading ui binary for linux/amd64 ...
  https://github.com/DeusData/codebase-memory-mcp/releases/latest/download/codebase-memory-mcp-ui-linux-amd64-portable.tar.gz
-#O=-#     #         #                                                                                                                                                                                                        curl: (22) The requested URL returned error: 404

error: download failed (exit 22)

Probably selecting 1 may work, I didn't test but just tried to reinstall using the script installer:

> curl -fsSL https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/install.sh | bash
codebase-memory-mcp installer
  os:      linux
  arch:    amd64
  target:  /home/cog5/.local/bin/codebase-memory-mcp

Downloading codebase-memory-mcp-linux-amd64-portable.tar.gz...
######################################################################## 100.0%
Checksum verified.
Extracting...
Verified candidate: codebase-memory-mcp 0.10.0
codebase-memory-mcp install 0.10.0

error: failed to stage install candidate: activation transaction I/O failed

Downloading the tar.gz directly and running install.sh manually also fails.

[mohammadrezwankhan]

[iandol]

Thanks! There was no log in ~/.cache/cagelab-memory-mcp/logs -- my ~/.cache parent directory has permissions of 775 is that what you are referring to, this is group writable, and it shouldn't be? Earlier versions of CBM had never flagged that I need to change permissions of the cache folder, and the current error is cryptic.

OK, I've now set ~/.cache to 755 and indeed the installer gets further than before, although now errors on agent setup:

codebase-memory-mcp installer
  os:      linux
  arch:    amd64
  target:  /home/cog5/.local/bin/codebase-memory-mcp

Downloading codebase-memory-mcp-linux-amd64-portable.tar.gz...
######################################################################## 100.0%
Checksum verified.
Extracting...
Verified candidate: codebase-memory-mcp 0.10.0
codebase-memory-mcp install 0.10.0

Stopping active CBM sessions and operations for install...
Installed binary -> /home/cog5/.local/bin/codebase-memory-mcp

Detected agents: Codex Gemini-CLI OpenCode VS-Code Hermes

Codex CLI:
error: agent_config agent=Codex CLI op=mcp_install path=/home/cog5/.codex/config.toml
  mcp: /home/cog5/.codex/config.toml
  instructions: /home/cog5/.codex/AGENTS.md
  skill: /home/cog5/.codex/skills/codebase-memory/SKILL.md (1 installed)
  agent: /home/cog5/.codex/agents/codebase-memory-scout.toml
  agent: /home/cog5/.codex/agents/codebase-memory.toml
  agent: /home/cog5/.codex/agents/codebase-memory-auditor.toml
error: agent_config agent=Codex CLI op=legacy_hook_cleanup path=/home/cog5/.codex/config.toml
  note: non-managed hooks require /hooks trust; definition changes require re-trust
Gemini CLI:
  mcp: /home/cog5/.gemini/settings.json
  instructions: /home/cog5/.gemini/GEMINI.md
  agent: /home/cog5/.gemini/agents/codebase-memory-scout.md
  agent: /home/cog5/.gemini/agents/codebase-memory.md
  agent: /home/cog5/.gemini/agents/codebase-memory-auditor.md
  hooks: BeforeTool + AfterTool read_file + SessionStart
  subagents: Scout + Verify + Auditor
OpenCode:
error: agent_config agent=OpenCode op=mcp_install path=/home/cog5/.config/opencode/opencode.json
  mcp: /home/cog5/.config/opencode/opencode.json
  instructions: /home/cog5/.config/opencode/AGENTS.md
  skill: /home/cog5/.config/opencode/skills/codebase-memory/SKILL.md (1 installed)
error: agent_config agent=OpenCode op=agent_install path=/home/cog5/.config/opencode/agents/codebase-memory-scout.md
error: agent_config agent=OpenCode op=agent_install path=/home/cog5/.config/opencode/agents/codebase-memory.md
error: agent_config agent=OpenCode op=agent_install path=/home/cog5/.config/opencode/agents/codebase-memory-auditor.md
  extension: /home/cog5/.config/opencode/plugins/cbm-augment.ts
VS Code:
  mcp: /home/cog5/.config/Code/User/mcp.json
VS Code:
  mcp: /home/cog5/.config/Code/User/profiles/52908607/mcp.json
VS Code:
  mcp: /home/cog5/.config/Code/User/profiles/-27ac4178/mcp.json
VS Code:
  mcp: /home/cog5/.config/Code/User/profiles/45aa3727/mcp.json
VS Code:
  mcp: /home/cog5/.config/Code/User/profiles/builtin/mcp.json
VS Code:
  mcp: /home/cog5/.config/Code/User/profiles/1a632d5a/mcp.json
VS Code:
  mcp: /home/cog5/.config/Code/User/profiles/5af2df1a/mcp.json
VS Code:
  mcp: /home/cog5/.config/Code/User/profiles/-33402880/mcp.json
Hermes:
error: agent_config agent=Hermes op=mcp_install path=/home/cog5/.hermes/config.yaml
  mcp: /home/cog5/.hermes/config.yaml
  skill: /home/cog5/.hermes/skills/codebase-memory/SKILL.md (1 installed)
error: agent_config agent=Hermes op=pre_llm_hook_install path=/home/cog5/.hermes/config.yaml
  skill: /home/cog5/.copilot/skills/codebase-memory/SKILL.md (1 installed)
  agent: /home/cog5/.copilot/agents/codebase-memory-scout.agent.md
  agent: /home/cog5/.copilot/agents/codebase-memory.agent.md
  agent: /home/cog5/.copilot/agents/codebase-memory-auditor.agent.md
  hooks: SessionStart + SubagentStart (dynamic graph context)
error: one or more agent configurations failed; the published/current executable was kept, and PATH/index cleanup was not attempted
error: activation stopped after one or more agent configuration or cleanup operations failed; the published/current executable was kept, and configuration changes that completed may remain. Please restart your coding-agent sessions after resolving the errors above.
Exception: bash exited with 1

I also now get a activation-events.ndjson but it doesn't give any more detail on what failed...

---

As an aside the update command is giving out-of-date or inconsistent advice:

> codebase-memory-mcp --version
codebase-memory-mcp 0.10.0

> codebase-memory-mcp update -y
codebase-memory-mcp update (current: 0.10.0)

The update runs from install.sh, not from this process. Run

  bash "/home/cog5/.local/bin/install.sh"

It downloads the latest release, verifies its checksum, and replaces
this binary in place. install.sh is idempotent, so re-running it IS
the update; pass --ui for the UI build.

There is no ~/.local/bin/install.sh after the installer. The install does not support a --ui option any more.

[DeusData]

Thanks for the thorough report, @iandol — you found two distinct bugs, and both are now slated for v0.10.2, the next fix release.

1. The variant chooser is obsolete — and not just in your old binary. As of v0.10.0 there is only ONE build per platform, with the graph UI always embedded; the ui-* archives no longer exist, which is why your "2) ui" choice 404s. What we hadn't realized until your report: the chooser still ships in current binaries too, offering a "ui" option that can only 404 and a "standard" option that quietly is the full UI build. Two fixes coming: the chooser is being removed entirely (update just downloads the one real archive), and we'll attach ui-*-named alias assets to releases so older 0.9.x binaries' updaters work again without you doing anything. Until then: choosing 1) standard gets you the complete product, UI included.

2. The install.sh failure is a real bug we're actively hunting — failed to stage install candidate: activation transaction I/O failed is also reported on WSL2 (#1535), and your report tells us it's broader than WSL2. Our current suspicion is the staging transaction's filesystem assumptions (cross-device renames on network/overlay filesystems). If you can share what filesystem your home / ~/.local/bin and /tmp are on (df -T ~/.local/bin /tmp), that would help us pin it — no worries if not.

Also worth grabbing when you retry: v0.10.1 fixes an important MCP output bug in 0.10.0 (tool results rendering empty in MCP clients).

Sorry for the bumpy upgrade, and thanks again — reports like this, with full transcripts of both paths, are exactly what makes fixes fast.

[DeusData]

Both issues are fixed in v0.10.2, released just now: https://github.com/DeusData/codebase-memory-mcp/releases/tag/v0.10.2

• The install failure was a permission policy, not I/O: a group-writable ~/.local (or any parent) was refused outright. Parents are now warned about rather than blocked, the install directory itself stays owner-private, and refusals name the directory and mode instead of claiming an I/O error.
• The obsolete ui/standard chooser is gone — and releases now also publish ui-*-named copies of each archive, so updaters in already-installed 0.9.x binaries (like the one that 404'd for you) resolve again with nothing required from you.

Thanks again for the detailed transcripts of both paths — they made this considerably faster to pin down.