Version
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?
E:\vibe-coding, Windows 11 Home, user david\89641, UAC medium integrity
▎
▎ Install: cbm 0.10.8 reports "installation failed (exit code 1)" with detail
▎ "agent configuration refresh or cleanup incomplete".
▎ Triggering op:
▎ error: agent_config agent=Codex CLI op=mcp_install path=C:\Users\89641\AppData\Roaming\orca\codex-runtime-home\home/config.toml (target: regular
▎ file, 5035 bytes)
▎
▎ Subsequent: every CLI invocation and stdio MCP request fails with
▎ "daemon session context was rejected"
▎ regardless of state:
▎ - CBM_DIAGNOSTICS=1 enabled
▎ - cache + rendezvous dir reset per official docs (rm -rf ~/.cache/codebase-memory-mcp/, cbm-daemon-*)
▎ - re-installed same0.10.8 binary multiple times
▎
▎ activation-events.ndjson consistently shows
▎ phase=failed detail="published/current binary retained; agent configuration refresh or cleanup incomplete"
▎
▎ Hypothesis: install's verification of Codex's config.toml rejects the file cbm itself> just wrote (same content, 5035 bytes), which aborts activation
▎ and leaves the cohort
▎ unheld, so daemon sessions can never claim.
Reproduction
▎ E:\vibe-coding, Windows 11 Home, user david\89641, UAC medium integrity
▎
▎ Install: cbm 0.10.8 reports "installation failed (exit code 1)" with detail
▎ "agent configuration refresh or cleanup incomplete".
▎ Triggering op:
▎ error: agent_config agent=Codex CLI op=mcp_install path=C:\Users\89641\AppData\Roaming\orca\codex-runtime-home\home/config.toml (target: regular
▎ file, 5035 bytes)
▎
▎ Subsequent: every CLI invocation and stdio MCP request fails with
▎ "daemon session context was rejected"
▎ regardless of state:
▎ - CBM_DIAGNOSTICS=1 enabled
▎ - cache + rendezvous dir reset per official docs (rm -rf ~/.cache/codebase-memory-mcp/, cbm-daemon-*)
▎ - re-installed same0.10.8 binary multiple times
▎
▎ activation-events.ndjson consistently shows
▎ phase=failed detail="published/current binary retained; agent configuration refresh or cleanup incomplete"
▎
▎ Hypothesis: install's verification of Codex's config.toml rejects the file cbm itself> just wrote (same content, 5035 bytes), which aborts activation
▎ and leaves the cohort
▎ unheld, so daemon sessions can never claim.
Logs
Diagnostics trajectory (memory / performance / leak issues)
Project scale (if relevant)
No response
Confirmations
Version
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?
E:\vibe-coding, Windows 11 Home, user david\89641, UAC medium integrity
▎
▎ Install: cbm 0.10.8 reports "installation failed (exit code 1)" with detail
▎ "agent configuration refresh or cleanup incomplete".
▎ Triggering op:
▎ error: agent_config agent=Codex CLI op=mcp_install path=C:\Users\89641\AppData\Roaming\orca\codex-runtime-home\home/config.toml (target: regular
▎ file, 5035 bytes)
▎
▎ Subsequent: every CLI invocation and stdio MCP request fails with
▎ "daemon session context was rejected"
▎ regardless of state:
▎ - CBM_DIAGNOSTICS=1 enabled
▎ - cache + rendezvous dir reset per official docs (rm -rf ~/.cache/codebase-memory-mcp/, cbm-daemon-*)
▎ - re-installed same0.10.8 binary multiple times
▎
▎ activation-events.ndjson consistently shows
▎ phase=failed detail="published/current binary retained; agent configuration refresh or cleanup incomplete"
▎
▎ Hypothesis: install's verification of Codex's config.toml rejects the file cbm itself> just wrote (same content, 5035 bytes), which aborts activation
▎ and leaves the cohort
▎ unheld, so daemon sessions can never claim.
Reproduction
▎ E:\vibe-coding, Windows 11 Home, user david\89641, UAC medium integrity
▎
▎ Install: cbm 0.10.8 reports "installation failed (exit code 1)" with detail
▎ "agent configuration refresh or cleanup incomplete".
▎ Triggering op:
▎ error: agent_config agent=Codex CLI op=mcp_install path=C:\Users\89641\AppData\Roaming\orca\codex-runtime-home\home/config.toml (target: regular
▎ file, 5035 bytes)
▎
▎ Subsequent: every CLI invocation and stdio MCP request fails with
▎ "daemon session context was rejected"
▎ regardless of state:
▎ - CBM_DIAGNOSTICS=1 enabled
▎ - cache + rendezvous dir reset per official docs (rm -rf ~/.cache/codebase-memory-mcp/, cbm-daemon-*)
▎ - re-installed same0.10.8 binary multiple times
▎
▎ activation-events.ndjson consistently shows
▎ phase=failed detail="published/current binary retained; agent configuration refresh or cleanup incomplete"
▎
▎ Hypothesis: install's verification of Codex's config.toml rejects the file cbm itself> just wrote (same content, 5035 bytes), which aborts activation
▎ and leaves the cohort
▎ unheld, so daemon sessions can never claim.
Logs
Diagnostics trajectory (memory / performance / leak issues)
Project scale (if relevant)
No response
Confirmations