This PR adds a new ZeroClaw template (v0.7.1-beta.1048), an AI personal assistant service written in Rust. The Compose file correctly follows all repository conventions (version 3.8, expose not ports, named volumes, restart policy). One question needs clarification before this can be considered fully functional: whether API_KEY is ZeroClaw's own gateway authentication token or the user's LLM provider credential.
API_KEY auto-generation (template.toml line 3): The password helper generates a random string that is mapped to API_KEY. If this is the user's OpenRouter (or other provider) API key, the service will deploy but all AI calls will fail because a randomly generated value is not a valid provider credential. Please clarify the intended semantics and, if it is an external credential, accept it as a user-provided input instead.
Confidence Score: 4/5
Safe to merge structurally, but the API_KEY semantics should be clarified to avoid a non-functional default deployment.
All Compose conventions are followed correctly. The only blocking question is whether the auto-generated API_KEY will cause the service to fail when connecting to an LLM provider — if API_KEY is ZeroClaw's internal gateway auth this is fine; if it is the provider credential it is P1 and needs to be user-supplied.
blueprints/zeroclaw/template.toml — clarify whether API_KEY should be auto-generated or user-provided.
🔄 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/805
**Author:** [@theonlyhennygod](https://github.com/theonlyhennygod)
**Created:** 4/18/2026
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `zeroclaw/update-v0.7.1-beta.1048`
---
### 📝 Commits (1)
- [`029a8fb`](https://github.com/Dokploy/templates/commit/029a8fb859e176b0713ec74bc8b26a74302482da) feat: add/update ZeroClaw template (v0.7.1-beta.1048)
### 📊 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 template (v0.7.1-beta.1048), an AI personal assistant service written in Rust. The Compose file correctly follows all repository conventions (version 3.8, `expose` not `ports`, named volumes, `restart` policy). One question needs clarification before this can be considered fully functional: whether `API_KEY` is ZeroClaw's own gateway authentication token or the user's LLM provider credential.
- **`API_KEY` auto-generation (`template.toml` line 3):** The `password` helper generates a random string that is mapped to `API_KEY`. If this is the user's OpenRouter (or other provider) API key, the service will deploy but all AI calls will fail because a randomly generated value is not a valid provider credential. Please clarify the intended semantics and, if it is an external credential, accept it as a user-provided input instead.
<h3>Confidence Score: 4/5</h3>
Safe to merge structurally, but the API_KEY semantics should be clarified to avoid a non-functional default deployment.
All Compose conventions are followed correctly. The only blocking question is whether the auto-generated API_KEY will cause the service to fail when connecting to an LLM provider — if API_KEY is ZeroClaw's internal gateway auth this is fine; if it is the provider credential it is P1 and needs to be user-supplied.
blueprints/zeroclaw/template.toml — clarify whether API_KEY should be auto-generated or user-provided.
<sub>Reviews (1): Last reviewed commit: ["feat: add/update ZeroClaw template (v0.7..."](https://github.com/dokploy/templates/commit/029a8fb859e176b0713ec74bc8b26a74302482da) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28869017)</sub>
> Greptile also left **2 inline comments** on this PR.
<!-- /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/805
Author: @theonlyhennygod
Created: 4/18/2026
Status: ❌ Closed
Base:
main← Head:zeroclaw/update-v0.7.1-beta.1048📝 Commits (1)
029a8fbfeat: add/update ZeroClaw template (v0.7.1-beta.1048)📊 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 template (v0.7.1-beta.1048), an AI personal assistant service written in Rust. The Compose file correctly follows all repository conventions (version 3.8,
exposenotports, named volumes,restartpolicy). One question needs clarification before this can be considered fully functional: whetherAPI_KEYis ZeroClaw's own gateway authentication token or the user's LLM provider credential.API_KEYauto-generation (template.tomlline 3): Thepasswordhelper generates a random string that is mapped toAPI_KEY. If this is the user's OpenRouter (or other provider) API key, the service will deploy but all AI calls will fail because a randomly generated value is not a valid provider credential. Please clarify the intended semantics and, if it is an external credential, accept it as a user-provided input instead.Confidence Score: 4/5
Safe to merge structurally, but the API_KEY semantics should be clarified to avoid a non-functional default deployment.
All Compose conventions are followed correctly. The only blocking question is whether the auto-generated API_KEY will cause the service to fail when connecting to an LLM provider — if API_KEY is ZeroClaw's internal gateway auth this is fine; if it is the provider credential it is P1 and needs to be user-supplied.
blueprints/zeroclaw/template.toml — clarify whether API_KEY should be auto-generated or user-provided.
Reviews (1): Last reviewed commit: "feat: add/update ZeroClaw template (v0.7..." | Re-trigger Greptile
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
[PR #805] feat: add/update ZeroClaw template (v0.7.1-beta.1048)to [PR #805] [CLOSED] feat: add/update ZeroClaw template (v0.7.1-beta.1048)