feat: add/update ZeroClaw template (v0.7.3)#810
Conversation
dosubot
Bot
added
size:S
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
|
||
| [config] | ||
| env = [ | ||
| "API_KEY=${api_key}", |
There was a problem hiding this comment.
API_KEY the gateway token or the provider credential?
The template auto-generates a random 64-character string for API_KEY using the ${password:64} helper. If ZeroClaw forwards this value to the upstream AI provider (OpenRouter etc.) to make LLM calls, a randomly generated value will be rejected and the assistant will fail to function after deployment. If it is ZeroClaw's own gateway token (protecting the public endpoint), auto-generation is the right approach — but the template would then need a separate variable for the user's real provider credential. Is API_KEY ZeroClaw's own gateway token, or the credential sent to the upstream AI provider? If the latter, it should be left blank for the user to fill in rather than auto-generated.
| [variables] | ||
| main_domain = "${domain}" | ||
| api_key = "${password:64}" | ||
|
|
||
| [config] | ||
| env = [ | ||
| "API_KEY=${api_key}", | ||
| "PROVIDER=openrouter", | ||
| "ZEROCLAW_ALLOW_PUBLIC_BIND=true", | ||
| "ZEROCLAW_GATEWAY_PORT=42617" | ||
| ] | ||
|
|
||
| [[config.domains]] | ||
| serviceName = "zeroclaw" | ||
| port = 42617 | ||
| host = "${main_domain}" |
There was a problem hiding this comment.
Per AGENTS.md, logos should be SVG format at approximately 128×128 px. A PNG file (zeroclaw.png) will render but won't scale as crisply in the UI. Consider replacing it with an SVG if one is available from the upstream project.
Context Used: AGENTS.md (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
2 participants
Summary
ghcr.io/zeroclaw-labs/zeroclaw:${VERSION}Checklist
Testing
Links
Greptile Summary
This PR adds a new ZeroClaw blueprint (v0.7.3) — a Rust-based AI personal assistant. The Docker Compose file follows all project conventions correctly, but two issues need attention before merging.
meta.json, which would silently drop Strapi from the template catalogue. This is likely a rebase/merge artefact; the branch should be rebased onto main andnpm run process-metare-run.API_KEYintemplate.tomlis auto-generated as a random 64-character string. If this is the credential ZeroClaw forwards to the upstream AI provider (OpenRouter), the deployment will fail because the provider will reject an arbitrary value. Clarification is needed on whether it is ZeroClaw's own gateway token or an upstream provider credential.Confidence Score: 3/5
Not safe to merge until the accidental Strapi removal is resolved and the API_KEY semantics are clarified.
Two P1 findings: (1) Strapi is silently removed from meta.json — a clear regression for existing users — and (2) the auto-generated API_KEY may render the ZeroClaw deployment non-functional if it is the upstream provider credential. Both need to be addressed before merging.
meta.json(Strapi removal) andblueprints/zeroclaw/template.toml(API_KEY semantics).Comments Outside Diff (1)
meta.json, line 5952-5969 (link)The diff removes the entire Strapi entry from
meta.json, but this PR's stated purpose is only to add ZeroClaw. Strapi disappears from the registry with no explanation, which would hide it from all users of the template catalogue. This is likely a merge/rebase conflict artefact from runningdedupe-and-sort-meta.json a branch that diverged from main. Please rebase onto the latest main, re-runnpm run process-meta, and verify Strapi (and any other entries) are preserved before merging.Reviews (1): Last reviewed commit: "feat: add/update ZeroClaw template (v0.7..." | Re-trigger Greptile
Context used: