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.
The diff unexpectedly removes the Strapi entry from 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 and npm run process-meta re-run.
The API_KEY in template.toml is 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) and blueprints/zeroclaw/template.toml (API_KEY semantics).
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 running dedupe-and-sort-meta.js on a branch that diverged from main. Please rebase onto the latest main, re-run npm run process-meta, and verify Strapi (and any other entries) are preserved before merging.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/810
**Author:** [@theonlyhennygod](https://github.com/theonlyhennygod)
**Created:** 4/19/2026
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `zeroclaw/update-v0.7.3`
---
### 📝 Commits (1)
- [`faa2454`](https://github.com/Dokploy/templates/commit/faa2454f0ba3d9b8685f3e64bd51a51e3cab23ea) feat: add/update ZeroClaw template (v0.7.3)
### 📊 Changes
**4 files changed** (+48 additions, -18 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/zeroclaw/docker-compose.yml` (+16 -0)
➕ `blueprints/zeroclaw/template.toml` (+16 -0)
➕ `blueprints/zeroclaw/zeroclaw.png` (+0 -0)
📝 `meta.json` (+16 -18)
</details>
### 📄 Description
## Summary
- Adds/updates ZeroClaw template to v${VERSION}
- Image: `ghcr.io/zeroclaw-labs/zeroclaw:${VERSION}`
- ZeroClaw is a fast, small, fully autonomous AI personal assistant (100% Rust)
- Multi-arch: linux/amd64 + linux/arm64
## Checklist
- [x] Read README.md suggestions
- [x] Tested template in personal Dokploy instance
- [x] Confirmed all requirements met
## Testing
- Deployed via Compose service import
- Service starts and gateway is accessible on port 42617
- Health check passes
## Links
- https://github.com/zeroclaw-labs/zeroclaw
- https://github.com/orgs/zeroclaw-labs/packages/container/package/zeroclaw
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
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.
- The diff unexpectedly removes the Strapi entry from `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 and `npm run process-meta` re-run.
- The `API_KEY` in `template.toml` is 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.
<h3>Confidence Score: 3/5</h3>
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) and `blueprints/zeroclaw/template.toml` (API_KEY semantics).
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (1)</h3></summary>
1. `meta.json`, line 5952-5969 ([link](https://github.com/dokploy/templates/blob/faa2454f0ba3d9b8685f3e64bd51a51e3cab23ea/meta.json#L5952-L5969))
<a href="#"><img alt="P1" src="https://greptile-static-assets.s3.amazonaws.com/badges/p1.svg?v=7" align="top"></a> **Unintended Strapi removal**
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 running `dedupe-and-sort-meta.js` on a branch that diverged from main. Please rebase onto the latest main, re-run `npm run process-meta`, and verify Strapi (and any other entries) are preserved before merging.
</details>
<!-- /greptile_failed_comments -->
<sub>Reviews (1): Last reviewed commit: ["feat: add/update ZeroClaw template (v0.7..."](https://github.com/dokploy/templates/commit/faa2454f0ba3d9b8685f3e64bd51a51e3cab23ea) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28887493)</sub>
> Greptile also left **2 inline comments** on this PR.
**Context used:**
- Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
<!-- /greptile_comment -->
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/810
Author: @theonlyhennygod
Created: 4/19/2026
Status: ❌ Closed
Base:
main← Head:zeroclaw/update-v0.7.3📝 Commits (1)
faa2454feat: add/update ZeroClaw template (v0.7.3)📊 Changes
4 files changed (+48 additions, -18 deletions)
View changed files
➕
blueprints/zeroclaw/docker-compose.yml(+16 -0)➕
blueprints/zeroclaw/template.toml(+16 -0)➕
blueprints/zeroclaw/zeroclaw.png(+0 -0)📝
meta.json(+16 -18)📄 Description
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:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
[PR #810] feat: add/update ZeroClaw template (v0.7.3)to [PR #810] [CLOSED] feat: add/update ZeroClaw template (v0.7.3)