docs: fix drift in Queue Management - #307
Draft
jack-arturo wants to merge 1 commit into
Draft
Conversation
Correct the --file example extension, the queue processing diagram's HTTP calls, the service-unavailable console output, the HealthStatus statistics fields, and the UpdateMemoryArgs parameter table. Verified against mcp-automem@92c2e33cb932b71d0df35fdc250778c6a51257af Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WdXojbwftVqDeiYvUDZ3JZ
Deploying automem-website with
|
| Latest commit: |
1d307e0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1584a600.automem-website.pages.dev |
| Branch Preview URL: | https://docs-audit-cli-queue-2026081.automem-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated docs-accuracy audit of
docs/cli/queue. Five proven discrepancies, capped at the per-PR limit. No open PR existed for this page.queue --file /path/to/memory-queue.jsonllrunQueueCommand) uses.jsonl.jsonllis a typo in a copy-pasteable commandlmcp-automem@92c2e33:src/cli/queue.ts#L116client.storeMemory()(POST /memory). There is no PATCH path anywhere inqueue.ts. Entries carryingrelatesToadditionally get aPOST /associateafter the store passmcp-automem@92c2e33:src/cli/queue.ts#L189,mcp-automem@92c2e33:src/cli/queue.ts#L219Checking AutoMem service at …,❌ Service unavailable - skipping queue processing,Queue will be retried on next runAutoMem endpoint unavailable; skipping queue drain.None of the three documented lines exists in the sourcemcp-automem@92c2e33:src/cli/queue.ts#L138HealthStatus.statisticshas four fields;falkordbandqdrantare typedstringmemory_count,vector_count,sync_status,vector_dimensions,enrichment— andfalkordb/qdrantareany, notstringmcp-automem@92c2e33:src/types.ts#L148UpdateMemoryArgsaccepts ten parameterst_validandt_invalid, which are the documented way to express a fact's shelf life instead of date tagsmcp-automem@92c2e33:src/types.ts#L314Verified against: mcp-automem@92c2e33cb932b71d0df35fdc250778c6a51257af
Checked and correct, left untouched: the endpoint priority chain (
AUTOMEM_API_URL/AUTOMEM_ENDPOINT→~/.claude.jsonmcpServers→http://127.0.0.1:8001), the--dry-runand--limitflags, the default queue path, the two-modeDeleteMemoryArgstable,destructiveHint: true, and the manual-recovery framing of the command.Questions
statistics.backendis documented as "alwaysautomem". The interface types it as a barestringand the value is set server-side, so the "always" is not verifiable from the client repo. Left alone since it may well be true in practice.Unverified
DETACH DELETE, Qdrant point removal) that lives inautomem, notmcp-automem; it matches what I saw while auditing the Memory Operations page in this same run, so I left it.Follow-ups
runQueueCommandthe file is read first, and a missing or empty file returns early withQueue file not found …/Memory queue empty.— the health check never runs in those cases.unlinked rather than truncated.memory_idand delegates to the client" under Delete Implementation predates the two-mode delete the table above it already documents.src/types.tslinks are pinned at538721c, several releases behind the audited SHA.Generated by Claude Code