Skip to content

Fix broken AlphaClaw Render deploy links - #1828

Closed
AlmogCohen wants to merge 1 commit into
garrytan:masterfrom
AlmogCohen:fix/render-deploy-link
Closed

AlmogCohen wants to merge 1 commit into
garrytan:masterfrom
AlmogCohen:fix/render-deploy-link

Conversation

@AlmogCohen

Copy link
Copy Markdown

Summary

  • Fixes the README "Deploy to Render" link to point at chrysb/openclaw-render-template instead of chrysb/alphaclaw
  • Replaces the bogus alphaclaw.com link in the personal-brain tutorial with the correct one-click Render deploy URL
  • Regenerates llms-full.txt via bun run build:llms

Why — README link

Render's Deploy button requires a render.yaml Blueprint Spec in the target repo.
chrysb/alphaclaw does not include one, so the current link does not prefill a
service and is not truly one-click.

AlphaClaw's own README uses the dedicated template repo:
https://github.com/chrysb/alphaclaw#deploy-recommended

That template repo includes render.yaml:
https://github.com/chrysb/openclaw-render-template/blob/main/render.yaml

Why — tutorial link

The personal-brain tutorial (Step 4) currently sends users to alphaclaw.com.
That domain is unrelated to the AlphaClaw OpenClaw harness — it resolves to a
pet-supply website ("Alpha Claw — Pawsitively the Best for Pets"). There is no
AlphaClaw product hosted there. The correct entry point is the Render one-click
deploy template linked above.

Test plan

  • Click the updated Render link — Render should show a prefilled AlphaClaw Docker web service
  • Confirm alphaclaw.com is no longer linked anywhere in the repo
  • bun run build:llms produces no diff beyond README change
  • bun test test/build-llms.test.ts passes (llms drift check)

Made with Cursor

Point the README deploy button at chrysb/openclaw-render-template (which
includes render.yaml) instead of chrysb/alphaclaw. Replace the personal-brain
tutorial's alphaclaw.com link with the same one-click Render URL and regenerate
llms-full.txt.
@garrytan

garrytan commented Jun 8, 2026

Copy link
Copy Markdown
Owner

Thanks for this contribution — and apologies for the slow triage. We did a full pass over the entire PR backlog. gbrain has moved fast, and the maintainer's larger "cathedral" rewrites have superseded a big share of community PRs: the AI gateway + recipes + user_provided_models system replaced almost all individual provider PRs; #1805 fixed the whole Postgres module-singleton class; #1542 unified the type taxonomy; #1657 the retrieval path; #1802 the doctor; and so on.

We're closing this one in that cleanup — either the fix already landed on master, it duplicates another PR or merged change, or it's outside the current merge bar. Where a closed PR carried a genuinely valuable idea, we've recorded it in docs/designs/COMMUNITY_IDEAS.md so nothing good is lost (a few may graduate into TODOs).

Please don't read the close as a judgment of the work — thank you for contributing. If you believe the underlying issue is still live on the latest master, reopen with a quick note and we'll take another look. 🙏

@garrytan garrytan closed this Jun 8, 2026
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