docs: fix drift in Guided Cloud Setup - #303
Draft
jack-arturo wants to merge 1 commit into
Draft
Conversation
Corrects three claims against mcp-automem@2816beb and automem@8ff266e: - headless note claimed CI/CODEX/CLAUDE_CODE/GITHUB_ACTIONS imply --yes; those only suppress the splash and GITHUB_ACTIONS is never read - reuse-an-existing-deployment flow is not reachable: the Railway provider returns no deployments, so every guided run deploys fresh - /health reports qdrant as "disconnected", never "unavailable" Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019Y3LbXh9Nn2xMybf9qx6ky
Deploying automem-website with
|
| Latest commit: |
da11926
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7a3ac0e3.automem-website.pages.dev |
| Branch Preview URL: | https://docs-audit-cli-guided-cloud-mp6w.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.
First review of
cli/guided-cloud-setup— no prior review-state memory existed for this page. Automated docs-accuracy audit.CI,CODEX,CLAUDE_CODE, orGITHUB_ACTIONSis set, the installer assumes--yes"shouldUseInstallerAnimation(), which only suppresses the animated splash.GITHUB_ACTIONSis not read anywhere insrc/. Nothing infers approval from the environment; the non-interactive path prints the plan and returns with "Re-run with --yes (or AUTOMEM_YES=1) to apply automatically"--yes, and that those vars only affect the splashCloudProviderimplementation and itslistDeployments()returns[]unconditionally — the source comment says "v1: always treat as a fresh deploy… the selector is skipped, so the user just deploys fresh". InstaPods is a link-and-paste flow with no listing at all. The reuse selector is therefore unreachable today\"qdrant\": \"unavailable\"is expected if you haven't configured Qdrant"/healthemits"connected" if qdrant_available else "disconnected"—"unavailable"is not a value the field can take. Losing Qdrant also flips top-levelstatusto"degraded""disconnected"and noted the accompanying"status": "degraded"Same
"qdrant": "unavailable"fabrication class previously fixed on Quick Start (#276) and Memory Operations (#271).Verified correct, no change needed: both interactive prompt blocks match
install.tsverbatim;CLOUD_PROVIDERSis exactlyinstapods | railway | other;AGENT_CLIENTSis exactlycodex, claude-code, cursor, openclaw, hermes; every flag/env pair in the table resolves (-yis a real alias for--yes);.envis written toenvironment.cwd;.bakbackups and the pre-config/healthverification are both real.Verified against: mcp-automem@2816beb7bb81d87bb8d592e8712fd8b4a7cc4f95
Verified against: automem@8ff266e62e65cb2e81719a765b05f64a2361a127
Questions
app.instapods.com/dashboard/pods/create?app=automem; the plan name and price live on InstaPods' side and are not asserted anywhere in this repo. Left as written, but it is unverifiable from source and will silently rot if InstaPods renames the tier.orchestrate.tsdoes gate on confirmation, but since the only live provider path is a fresh Railway deploy, I could not confirm the confirmation text names a plan. Left alone.Unverified
/img/docs/installer-cloud-provider.pngrenders the provider prompt; I checked the prompt strings in source but not the image contents.PORTassignment behavior (thePORT=8001caution) is Railway platform behavior, not something these repos assert.Follow-ups
--client(singular, repeatable), whichparseInstallArgsaccepts alongside--clients. Completeness gap, not an error.Generated by Claude Code