[PR #758] feat: add/update ZeroClaw template (v0.6.5) #5072

New Issue

GiteaMirror · 2026-05-06T17:54:49-05:00

GiteaMirror commented

2026-05-06 17:54:49 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/758
Author: @theonlyhennygod
Created: 3/27/2026
Status: 🔄 Open

Base: main ← Head: zeroclaw/update-v0.6.5

📝 Commits (1)

6ab1588 feat: add/update ZeroClaw template (v0.6.5)

📊 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

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

Read README.md suggestions
Tested template in personal Dokploy instance
Confirmed all requirements met

Testing

Deployed via Compose service import
Service starts and gateway is accessible on port 42617
Health check passes

Links

Greptile Summary

This PR adds the ZeroClaw v0.6.5 template (a 100% Rust autonomous AI assistant). The blueprint structure is mostly correct — version: "3.8", expose instead of ports, named volume, and restart: unless-stopped all follow the project conventions. However, two blocking issues need to be resolved before merging:

API_KEY auto-generation (template.toml): The template assigns a randomly-generated 64-character string to API_KEY, which is the user's AI-provider credential (e.g. OpenRouter key). This will cause ZeroClaw to fail authentication with the AI provider immediately on deployment. The field should require the user to supply their own key.
Accidental Strapi removal (meta.json): The Strapi entry was silently deleted from meta.json even though the blueprints/strapi/ directory (with all blueprint files) still exists. This is almost certainly an unintentional side-effect of a merge conflict and must be restored before this PR lands.

Minor: the logo is PNG rather than the project-preferred SVG format, but this is non-blocking.

Confidence Score: 2/5

Not safe to merge — accidental Strapi removal from meta.json and a broken API_KEY default that prevents ZeroClaw from working need to be fixed first.

Two P1 issues block merge: the Strapi entry deletion is a clear regression for an existing template, and auto-generating the AI-provider API key will produce a non-functional deployment out-of-the-box. Both are straightforward to fix but must be addressed.

blueprints/zeroclaw/template.toml (api_key default) and meta.json (Strapi removal)

Important Files Changed

Filename	Overview
blueprints/zeroclaw/docker-compose.yml	New compose file is structurally correct — version 3.8, uses `expose` not `ports`, has `restart: unless-stopped`, named volume, service name matches blueprint folder.
blueprints/zeroclaw/template.toml	Auto-generates `api_key` with a random password helper, but `API_KEY` is the user's AI-provider credential — the service will fail to authenticate out-of-the-box.
meta.json	Adds ZeroClaw entry correctly, but unexpectedly removes the Strapi entry even though the blueprint directory still exists — likely an accidental merge conflict artifact.
blueprints/zeroclaw/zeroclaw.png	Logo PNG added. SVG is preferred per project guidelines but PNG is functional.

Comments Outside Diff (1)

blueprints/zeroclaw/zeroclaw.png

Logo format: PNG instead of preferred SVG

Per the project's AGENTS.md style guide, SVG is the preferred logo format (~128×128 px). PNG will work but lacks the resolution-independence of SVG. If a vector version of the ZeroClaw logo is available, swapping to .svg would be preferable.

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!}

_{Reviews (1): Last reviewed commit: "feat: add/update ZeroClaw template (v0.6..." | Re-trigger Greptile}

Greptile also left 2 inline comments on this PR.

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

Context used:

Context used - AGENTS.md (source)

_{🔄 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/758 **Author:** [@theonlyhennygod](https://github.com/theonlyhennygod) **Created:** 3/27/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `zeroclaw/update-v0.6.5` --- ### 📝 Commits (1) - [`6ab1588`](https://github.com/Dokploy/templates/commit/6ab1588aafd89eaa4c319f690913c8ac3f32e1c0) feat: add/update ZeroClaw template (v0.6.5) ### 📊 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  <h3>Greptile Summary</h3> This PR adds the ZeroClaw v0.6.5 template (a 100% Rust autonomous AI assistant). The blueprint structure is mostly correct — `version: "3.8"`, `expose` instead of `ports`, named volume, and `restart: unless-stopped` all follow the project conventions. However, two blocking issues need to be resolved before merging: - **`API_KEY` auto-generation (template.toml):** The template assigns a randomly-generated 64-character string to `API_KEY`, which is the user's AI-provider credential (e.g. OpenRouter key). This will cause ZeroClaw to fail authentication with the AI provider immediately on deployment. The field should require the user to supply their own key. - **Accidental Strapi removal (meta.json):** The Strapi entry was silently deleted from `meta.json` even though the `blueprints/strapi/` directory (with all blueprint files) still exists. This is almost certainly an unintentional side-effect of a merge conflict and must be restored before this PR lands. Minor: the logo is PNG rather than the project-preferred SVG format, but this is non-blocking. <h3>Confidence Score: 2/5</h3> Not safe to merge — accidental Strapi removal from meta.json and a broken API_KEY default that prevents ZeroClaw from working need to be fixed first. Two P1 issues block merge: the Strapi entry deletion is a clear regression for an existing template, and auto-generating the AI-provider API key will produce a non-functional deployment out-of-the-box. Both are straightforward to fix but must be addressed. `blueprints/zeroclaw/template.toml` (api_key default) and `meta.json` (Strapi removal) <details><summary><h3>Important Files Changed</h3></summary> | Filename | Overview | |----------|----------| | blueprints/zeroclaw/docker-compose.yml | New compose file is structurally correct — version 3.8, uses `expose` not `ports`, has `restart: unless-stopped`, named volume, service name matches blueprint folder. | | blueprints/zeroclaw/template.toml | Auto-generates `api_key` with a random password helper, but `API_KEY` is the user's AI-provider credential — the service will fail to authenticate out-of-the-box. | | meta.json | Adds ZeroClaw entry correctly, but unexpectedly removes the Strapi entry even though the blueprint directory still exists — likely an accidental merge conflict artifact. | | blueprints/zeroclaw/zeroclaw.png | Logo PNG added. SVG is preferred per project guidelines but PNG is functional. | </details> </details>  <details><summary><h3>Comments Outside Diff (1)</h3></summary> 1. `blueprints/zeroclaw/zeroclaw.png` <a href="#"><img alt="P2" src="https://greptile-static-assets.s3.amazonaws.com/badges/p2.svg?v=7" align="top"></a> **Logo format: PNG instead of preferred SVG** Per the project's `AGENTS.md` style guide, SVG is the preferred logo format (~128×128 px). PNG will work but lacks the resolution-independence of SVG. If a vector version of the ZeroClaw logo is available, swapping to `.svg` would be preferable. **Context Used:** AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2)) <sub>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!</sub> </details>  <sub>Reviews (1): Last reviewed commit: ["feat: add/update ZeroClaw template (v0.6..."](https://github.com/dokploy/templates/commit/6ab1588aafd89eaa4c319f690913c8ac3f32e1c0) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=26530632)</sub> > Greptile also left **2 inline comments** on this PR. <sub>(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!</sub> **Context used:** - Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))  --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-06 17:54:49 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#5072