docs: refresh cli config-tools release pin - #354
Conversation
Deploying automem-website with
|
| Latest commit: |
6012f08
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e6bb74ec.automem-website.pages.dev |
| Branch Preview URL: | https://docs-mcp-automem-config-tool.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: 6012f081a6
ℹ️ 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".
|
|
||
| This page explains how to configure the mcp-automem client to connect to your AutoMem service. It covers environment variables, configuration resolution priority, platform-specific configuration files, and validation. For initial setup instructions, see [Setup & Installation](/docs/cli/setup/). For platform-specific integration details, see [Platform Installers](/docs/cli/platform-installers/). | ||
|
|
||
| The examples on this page are pinned to the audited `mcp-automem` `0.16.0` release commit `9a0bbf754dd31db524da25638b0e97907e32ff37`. |
There was a problem hiding this comment.
The new release-pin claim leaves the environment-variable reference incomplete: the repository's pinned audit at .github/docs-pr-reconciliation/audits/release-audit-final.md:64 identifies AUTOMEM_PARENT_WATCHDOG_MS as a supported 0.16.0 runtime setting, with a 30,000 ms default, POSIX-only effect, and no disable value, and explicitly requires a row here. Operators needing to tune lifecycle polling therefore cannot discover this setting from the page now presented as release-audited.
Useful? React with 👍 / 👎.
| ``` | ||
|
|
||
| The debug output shows the resolved `endpoint` and whether an `apiKey` was found (the actual key value is masked for security). | ||
| Expect the narrow stderr lines above rather than per-tool traces, HTTP dumps, or retry/backoff logs. |
There was a problem hiding this comment.
When configuration resolution behaves unexpectedly, the preceding text still tells users to enable debug mode “to see which values are being loaded,” but this replacement now correctly states that the audited output contains only the conditional process-title line and the server-start line. Neither reveals the resolved endpoint, key presence, or winning source, so following this troubleshooting step cannot diagnose the stated problem; replace it with an actual way to inspect the effective configuration rather than merely telling readers to expect no traces.
Useful? React with 👍 / 👎.
1 participant
Summary
cli/config-toolsexamples and resolution diagrams with release-pinnedmcp-automem0.16.0 behavior from9a0bbf754dd31db524da25638b0e97907e32ff37AUTOMEM_API_URL→CLAUDE_PLUGIN_OPTION_API_URL→AUTOMEM_ENDPOINT→ default, whileresolveAutoMemConfig()for the queue CLI documentsAUTOMEM_API_URL→AUTOMEM_ENDPOINT→~/.claude.json→ defaultmemorykey without-y, while updating the Codex TOML example to the shipped[mcp_servers.memory]/[mcp_servers.memory.env]form with-yrecall --queryinvocation and narrow the documented debug stderr output to the auditedAutoMem MCP server runningline plus the process-tag pathVerification
node --test tests/config-tools-docs.test.mjsnode --test tests/*.test.mjsnode scripts/build-pages.mjsAudit References
mcp-automem0.16.0 at9a0bbf754dd31db524da25638b0e97907e32ff37#324and#282Notes