Replies: 7 comments 1 reply
|
i met this error while install config for hermes and it mean fail to edit add pre_llm hooks for some reason. It success to add codebase-memory-mcp to mcp_servers but fail to add hooks so i just add it manual into config.yaml, for me its like: hooks:
pre_llm_call:
- command: C:/Users/Administrator/AppData/Local/Programs/codebase-memory-mcp/codebase-memory-mcp.exe hook-augment --dialect hermesYou can try add that but with different PATH for you then try install again with --skip-config (maybe no need?) and test if it work in hermes |
|
@iandol — thank you for the kind words, genuinely. And I'm sorry: you have now hit install problems across three consecutive releases, and each time you have responded by writing a careful report instead of walking away. That patience is worth more to this project than the fixes are. Your hypothesis is right, and it is fixed. OpenCode reads either The install target is now whichever file already exists, On Hermes, I don't yet have an explanation, and I would rather say so than guess. The ls -la ~/.hermes/ && codebase-memory-mcp install --plan 2>&1 | tail -30Two specific things worth checking meanwhile: whether Also worth noting: the Thank you again. v0.10.3 also fixes a group-writable-directory refusal that was blocking installs for other people in a similar way, so it is worth re-running the installer once it lands. |
|
Heads-up: the OpenCode fix is merged and v0.10.3 is building now. (#1575, merged as Once it publishes, re-running the installer should put the cbm entry into your existing The same release carries three other install fixes that may be relevant to people arriving at this thread: a permission rule that refused ordinary group-writable home directories, an error that reported Hermes is still open — that failure is on a different path and this release will not fix it. Whenever you have a moment, the |
|
v0.10.3 is published — https://github.com/DeusData/codebase-memory-mcp/releases/tag/v0.10.3 @iandol, the OpenCode fix is in it: the installer now targets your existing Hermes remains open and unaddressed by this release; whenever you have a moment, the |
|
Hi @DeusData thanks for the super fast fixes and advice, much appreciated! Running that command on V0.10.2 before I upgrade to V0.10.3: Hope it helps, if there is anything else we can do let us know! |
|
Not so related, but I'll post here and we can move it to its own spot if required (I use the curl | bash install): That script was not installed on my Ubuntu system for some reason... |
|
On updating to V0.10.3 (and deleting my We are down from 2 to 1 errors for Hermes, the same OpenCode error as before. I also see two errors in Codex (I think they were there before but I rarely use Codex directly so didn't highlight it in the original post). |
Uh oh!
There was an error while loading. Please reload this page.
First off thanks to @DeusData for his amazing support and infectiously positive replies to the update/install issues some of us faced. Martin you are an amazingly responsive developer, kudos!!!
With V0.10.2 after trying to ensure my permissions are
755for my various paths I still see some errors with agent setup:The error is not complaining about permissions but something else. It isn't clear what is the issue. I wonder for opencode if the problem is that opencode supports BOTH .json and .jsonc files -- CBM seems to write to
opencode.jsonwhereas my actual config isopencode.jsonc-- possibly the install should check foropencode.jsoncfirst then fallback toopencode.json.https://opencode.ai/docs/config/#format
Perhaps that is a red herring and a different error is at fault? The MCP config is in
opencode.jsonso perhaps this error is a false alarm?I see errors for Hermes too, also not clear what the cause is:
All reactions