Feat. Request: detect_changes capability

[OannesGPT]

Dear All,

"I'm looking at the current state of the MCP tool surface—there's no detect_changes capability, so I'm falling back on git status and git diff to track what's happening."

Based on this 'seam' this seems like a useful addition to the ecosystem here?

Thanks for the consideration! Most of amazing open sourced tool I used so far!

Much Love!
H.

[DeusData]

Thanks for the suggestion and the kind words. detect_changes is already part of the current MCP tool surface.

If your client does not see it, the most likely causes are an older binary or cached tool discovery. Could you share the output of codebase-memory-mcp --version, the client you are using, and its current tools/list result after fully restarting the MCP connection? That should tell us whether this is a discovery issue or an outdated installation.

[DeusData]

Thank you again for the suggestion. Checking back on the discovery question: can your client now see detect_changes after reconnecting? If it is still missing, the CBM version, client, and refreshed tool-list result would help identify the gap. There is no need to design a new tool before establishing what the client is actually exposing.