docs: fix drift in Configuration Tools - #282
Conversation
- JSON/TOML examples register the server as "memory", not "automem" - Codex TOML uses [mcp_servers.memory], not [[mcp_servers]] with name - env-resolution diagram now reflects resolveAutoMemApiUrl() precedence - document AUTOMEM_PARENT_WATCHDOG_MS Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013aFijMh5z5WBKN73zhxXz7
Deploying automem-website with
|
| Latest commit: |
0d1f9fb
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://dc4e6721.automem-website.pages.dev |
| Branch Preview URL: | https://docs-audit-cli-config-tools-612h.automem-website.pages.dev |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0d1f9fb9db
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ``` | ||
|
|
||
| The `command` and `args` launch the MCP server in stdio mode. The `env` block passes configuration to the server process. Platform launchers spawn this command when initializing MCP connections. | ||
| The server is registered under the key `memory` — that key becomes the tool-name prefix, so the tools resolve as `mcp__memory__store_memory`, `mcp__memory__recall_memory`, and so on. The `command` and `args` launch the MCP server in stdio mode. The `env` block passes configuration to the server process. Platform launchers spawn this command when initializing MCP connections. |
There was a problem hiding this comment.
In the shared JSON example, this sentence applies the Claude-style mcp__memory__... names to Claude Desktop, Cursor, and Claude Code, but Cursor exposes MCP tools with underscore-delimited names (mcp_memory_recall_memory for the same memory server, as documented in src/content/docs/docs/platforms/cursor.md). For users following this common configuration page in Cursor, the listed tool names will not exist, so the sentence should either be scoped to Claude clients or include Cursor's separate prefix format.
Useful? React with 👍 / 👎.
|
Superseded by merged #354. This fresh replacement was rebuilt from current main against mcp-automem 0.16.0@9a0bbf754dd31db524da25638b0e97907e32ff37, then corrected through independent review with focused tests, full tests, build, and deployment checks. |
|
Closing now that every release-validated claim is carried by merged replacement #354. The legacy branch is preserved. |
2 participants
Routine docs-accuracy audit of
cli/config-tools. Last reviewed ~2026-07-08;src/cli/migrate.tsandtemplates/**have changed inmcp-automemsince.The two config examples on this page were both copy-pasteable and both wrong, which is the reason this is not a draft — every fix is a value or a path, no prose reinterpretation.
Fixes
"mcpServers": { "automem": … }withargs: ["@verygoodplugins/mcp-automem"]"memory"withargs: ["-y", "@verygoodplugins/mcp-automem"]. The key is the tool-name prefix, soautomemyieldsmcp__automem__*and breaks every documentedmcp__memory__*tool reference and the hook matchers theclaude-codeinstaller writes.[[mcp_servers]](array of tables) with aname = "automem"key and[mcp_servers.env][mcp_servers.memory], with env in[mcp_servers.memory.env]. There is nonamekey and no array-of-tables form. As written the snippet does not register a server.AUTOMEM_API_URL exists?check falling through to the default; key priority listed as 2 entriesresolveAutoMemApiUrl()walks three sources before defaulting (AUTOMEM_API_URL→CLAUDE_PLUGIN_OPTION_API_URL→AUTOMEM_ENDPOINT), skipping blanks.readAutoMemApiKeyFromEnv()walks four. The diagram contradicted the prose directly above it, which already lists all four key tiers.AUTOMEM_PARENT_WATCHDOG_MSsrc/index.ts#L1771viaparseWatchdogIntervalMs, default 30000, POSIX-only, cannot be disabledVerified against: verygoodplugins/mcp-automem@cbeb3cb
Verified correct and left untouched:
resolveAutoMemConfig()really does live insrc/cli/queue.ts(L60) with the documented env →~/.claude.json→ default order; thereadAutoMemApiKeyFromEnv()4-tier prose list including bothCLAUDE_PLUGIN_OPTION_*casings;AUTOMEM_PROCESS_TAG/MCP_PROCESS_TAG(src/index.ts#L89);AUTOMEM_LOG_LEVEL=debug;AUTOMEM_RECALL_TOKEN_BUDGETdefault 18000; content-size governance 500 soft / 2000 hard (src/index.ts#L1455-L1456);recall,queue, andconfigall present inKNOWN_COMMANDS; the dotenvquietbehavior; and the OpenClaw config path~/.openclaw/openclaw.json(src/cli/openclaw.ts#L403).Questions
claude mcp addrather than a hand-edited~/.claude.json. Is showing the raw JSON here still the intended guidance, or should it point at the CLI?Unverified
AUTOMEM_LOG_LEVEL=debugis read in two places, but I did not trace which of these four categories each debug branch actually emits.Follow-ups
hermes,copilot,antigravity,migrate, anduninstall.~/.openclaw/openclaw.jsonis the first of three probed config paths (config.json5andconfig.jsonfollow); the table presents it as the only one.Generated by Claude Code