Skip to content

docs: fix drift in Guided Cloud Setup - #303

Draft
jack-arturo wants to merge 1 commit into
mainfrom
docs/audit-cli-guided-cloud-setup-20260813
Draft

docs: fix drift in Guided Cloud Setup#303
jack-arturo wants to merge 1 commit into
mainfrom
docs/audit-cli-guided-cloud-setup-20260813

Conversation

@jack-arturo

Copy link
Copy Markdown
Member

First review of cli/guided-cloud-setup — no prior review-state memory existed for this page. Automated docs-accuracy audit.

Claim Current state Fix Evidence
"When CI, CODEX, CLAUDE_CODE, or GITHUB_ACTIONS is set, the installer assumes --yes" Those three env vars appear in exactly one place — shouldUseInstallerAnimation(), which only suppresses the animated splash. GITHUB_ACTIONS is not read anywhere in src/. 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" Rewrote the note to say the installer never infers --yes, and that those vars only affect the splash mcp-automem@2816beb:src/cli/install-ui.ts#L188-L190, src/cli/install.ts#L1364-L1374
"If your provider account already has AutoMem deployments, the installer lists them and lets you reuse an existing one… An empty account goes straight to a fresh deploy" Railway is the only CloudProvider implementation and its listDeployments() 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 Kept the description of the reuse path but added a note that it is not wired up for Railway, and pointed users at Other — I already have a URL + key mcp-automem@2816beb:src/cli/cloud/railway.ts#L312-L317
Two troubleshooting rows resolve to "choose reuse an existing deployment" / "choose the existing deployment to reuse its credentials" Same as above — that choice is never offered Both rows now route to the Other provider option; the "charged twice" row states the real cause mcp-automem@2816beb:src/cli/cloud/railway.ts#L315
"\"qdrant\": \"unavailable\" is expected if you haven't configured Qdrant" /health emits "connected" if qdrant_available else "disconnected""unavailable" is not a value the field can take. Losing Qdrant also flips top-level status to "degraded" Corrected to "disconnected" and noted the accompanying "status": "degraded" automem@8ff266e:automem/api/health.py#L90, #L71-L76

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.ts verbatim; CLOUD_PROVIDERS is exactly instapods | railway | other; AGENT_CLIENTS is exactly codex, claude-code, cursor, openclaw, hermes; every flag/env pair in the table resolves (-y is a real alias for --yes); .env is written to environment.cwd; .bak backups and the pre-config /health verification are both real.

Verified against: mcp-automem@2816beb7bb81d87bb8d592e8712fd8b4a7cc4f95
Verified against: automem@8ff266e62e65cb2e81719a765b05f64a2361a127

Questions

  • InstaPods "Grow plan ($15/mo flat)" — the installer only opens 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.
  • "Any billable deploy is gated behind an explicit confirmation that names the plan"orchestrate.ts does 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

  • The screenshot /img/docs/installer-cloud-provider.png renders the provider prompt; I checked the prompt strings in source but not the image contents.
  • Railway's own per-service PORT assignment behavior (the PORT=8001 caution) is Railway platform behavior, not something these repos assert.

Follow-ups

  • The flag table omits --client (singular, repeatable), which parseInstallArgs accepts alongside --clients. Completeness gap, not an error.

Generated by Claude Code

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
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying automem-website with  Cloudflare Pages  Cloudflare Pages

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

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants