ZeroClaw is a fast, small, fully autonomous AI personal assistant infrastructure (100% Rust)
What is ZeroClaw?
Open-source AI agent daemon. Connects to any LLM provider (OpenRouter, OpenAI, Anthropic, Ollama), exposes a web dashboard + REST/WebSocket API on port 42617. Features: persistent memory, multi-channel chat (Discord, Telegram, Matrix, Slack, WhatsApp, Nostr, Lark), scheduled tasks, autonomous tool use.
Service starts and gateway is accessible on port 42617
Health check passes
Files
blueprints/zeroclaw/docker-compose.yml
blueprints/zeroclaw/template.toml
blueprints/zeroclaw/zeroclaw.png (logo)
meta.json (added entry)
Greptile Summary
This PR adds a new ZeroClaw template (v0.6.4), a Rust-based autonomous AI assistant daemon that exposes a web dashboard and REST/WebSocket API on port 42617. The implementation is clean and follows all repository conventions.
All required Compose conventions are met: version: "3.8", service name matches the folder (zeroclaw), restart: unless-stopped, expose instead of ports, no container_name or custom networks, and a named persistent volume.
template.toml generates a random 64-character API_KEY and correctly maps the domain to port 42617.
The meta.json entry contains all required fields (id, name, version, description, logo, links, tags); the version 0.6.4 matches the Docker image tag exactly.
The apparent removal of the strapi entry from meta.json is not a regression — the base branch contained a duplicate strapi entry, and the dedupe-and-sort-meta.js script correctly removed the extra copy.
Two minor style suggestions: the ${PROVIDER:-openrouter} default in docker-compose.yml is redundant (template.toml already injects the value), and PROVIDER could optionally be surfaced as a configurable template variable to make it easier for users to switch LLM providers at deploy time.
Confidence Score: 5/5
Safe to merge — no functional or security issues; all template conventions are met.
The ZeroClaw template follows every hard requirement from AGENTS.md: correct Compose version, proper service naming, no forbidden directives, pinned image, no hardcoded secrets, and a valid meta.json entry. The only open items are two non-blocking P2 style suggestions. The Strapi removal is correct deduplication and not a regression.
No files require special attention.
Important Files Changed
Filename
Overview
blueprints/zeroclaw/docker-compose.yml
New Compose file following all conventions: version 3.8, service named zeroclaw (matches folder), restart: unless-stopped, expose instead of ports, named volume. Minor: ${PROVIDER:-openrouter} fallback is redundant with the explicit PROVIDER=openrouter injected by template.toml.
blueprints/zeroclaw/template.toml
New template config. Generates a 64-char API key, maps the domain, and wires it to port 42617. PROVIDER is hardcoded to openrouter — functional but not user-configurable through the Dokploy UI.
meta.json
Adds the zeroclaw entry with all required fields; version 0.6.4 matches the Docker image tag. The removal of one strapi block is correct deduplication — the base branch had two identical strapi entries and dedupe-and-sort-meta.js removed one.
🔄 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/757
**Author:** [@theonlyhennygod](https://github.com/theonlyhennygod)
**Created:** 3/26/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `zeroclaw/add-template`
---
### 📝 Commits (1)
- [`ddb45fc`](https://github.com/Dokploy/templates/commit/ddb45fc4ec29980f5811806a6f50775414697412) feat: add ZeroClaw template (v0.6.4)
### 📊 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 ZeroClaw template (v0.6.4)
- Image: `ghcr.io/zeroclaw-labs/zeroclaw:0.6.4` (multi-arch: linux/amd64 + linux/arm64)
- ZeroClaw is a fast, small, fully autonomous AI personal assistant infrastructure (100% Rust)
## What is ZeroClaw?
Open-source AI agent daemon. Connects to any LLM provider (OpenRouter, OpenAI, Anthropic, Ollama), exposes a web dashboard + REST/WebSocket API on port 42617. Features: persistent memory, multi-channel chat (Discord, Telegram, Matrix, Slack, WhatsApp, Nostr, Lark), scheduled tasks, autonomous tool use.
- GitHub: https://github.com/zeroclaw-labs/zeroclaw
- Docker: https://github.com/orgs/zeroclaw-labs/packages/container/package/zeroclaw
## Checklist
- [x] Read README.md suggestions
- [x] Tested template in personal Dokploy instance
- [x] Confirmed all requirements met
- [x] No `ports`, `container_name`, or custom networks
- [x] Pinned image version (not `latest`)
- [x] No hardcoded secrets (uses Dokploy helpers)
- [x] Ran `dedupe-and-sort-meta.js`
## Testing
- Deployed via Compose service import
- Service starts and gateway is accessible on port 42617
- Health check passes
## Files
- `blueprints/zeroclaw/docker-compose.yml`
- `blueprints/zeroclaw/template.toml`
- `blueprints/zeroclaw/zeroclaw.png` (logo)
- `meta.json` (added entry)
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds a new **ZeroClaw** template (v0.6.4), a Rust-based autonomous AI assistant daemon that exposes a web dashboard and REST/WebSocket API on port 42617. The implementation is clean and follows all repository conventions.
- All required Compose conventions are met: `version: "3.8"`, service name matches the folder (`zeroclaw`), `restart: unless-stopped`, `expose` instead of `ports`, no `container_name` or custom networks, and a named persistent volume.
- `template.toml` generates a random 64-character `API_KEY` and correctly maps the domain to port 42617.
- The `meta.json` entry contains all required fields (`id`, `name`, `version`, `description`, `logo`, `links`, `tags`); the version `0.6.4` matches the Docker image tag exactly.
- The apparent removal of the `strapi` entry from `meta.json` is **not** a regression — the base branch contained a duplicate `strapi` entry, and the `dedupe-and-sort-meta.js` script correctly removed the extra copy.
- Two minor style suggestions: the `${PROVIDER:-openrouter}` default in `docker-compose.yml` is redundant (template.toml already injects the value), and `PROVIDER` could optionally be surfaced as a configurable template variable to make it easier for users to switch LLM providers at deploy time.
<h3>Confidence Score: 5/5</h3>
Safe to merge — no functional or security issues; all template conventions are met.
The ZeroClaw template follows every hard requirement from AGENTS.md: correct Compose version, proper service naming, no forbidden directives, pinned image, no hardcoded secrets, and a valid meta.json entry. The only open items are two non-blocking P2 style suggestions. The Strapi removal is correct deduplication and not a regression.
No files require special attention.
<details><summary><h3>Important Files Changed</h3></summary>
| Filename | Overview |
|----------|----------|
| blueprints/zeroclaw/docker-compose.yml | New Compose file following all conventions: version 3.8, service named zeroclaw (matches folder), restart: unless-stopped, expose instead of ports, named volume. Minor: ${PROVIDER:-openrouter} fallback is redundant with the explicit PROVIDER=openrouter injected by template.toml. |
| blueprints/zeroclaw/template.toml | New template config. Generates a 64-char API key, maps the domain, and wires it to port 42617. PROVIDER is hardcoded to openrouter — functional but not user-configurable through the Dokploy UI. |
| meta.json | Adds the zeroclaw entry with all required fields; version 0.6.4 matches the Docker image tag. The removal of one strapi block is correct deduplication — the base branch had two identical strapi entries and dedupe-and-sort-meta.js removed one. |
</details>
</details>
<sub>Reviews (1): Last reviewed commit: ["feat: add ZeroClaw template (v0.6.4)"](https://github.com/dokploy/templates/commit/ddb45fc4ec29980f5811806a6f50775414697412) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=26496669)</sub>
> Greptile also left **2 inline comments** on this PR.
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
**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/757
Author: @theonlyhennygod
Created: 3/26/2026
Status: 🔄 Open
Base:
main← Head:zeroclaw/add-template📝 Commits (1)
ddb45fcfeat: add ZeroClaw template (v0.6.4)📊 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:0.6.4(multi-arch: linux/amd64 + linux/arm64)What is ZeroClaw?
Open-source AI agent daemon. Connects to any LLM provider (OpenRouter, OpenAI, Anthropic, Ollama), exposes a web dashboard + REST/WebSocket API on port 42617. Features: persistent memory, multi-channel chat (Discord, Telegram, Matrix, Slack, WhatsApp, Nostr, Lark), scheduled tasks, autonomous tool use.
Checklist
ports,container_name, or custom networkslatest)dedupe-and-sort-meta.jsTesting
Files
blueprints/zeroclaw/docker-compose.ymlblueprints/zeroclaw/template.tomlblueprints/zeroclaw/zeroclaw.png(logo)meta.json(added entry)Greptile Summary
This PR adds a new ZeroClaw template (v0.6.4), a Rust-based autonomous AI assistant daemon that exposes a web dashboard and REST/WebSocket API on port 42617. The implementation is clean and follows all repository conventions.
version: "3.8", service name matches the folder (zeroclaw),restart: unless-stopped,exposeinstead ofports, nocontainer_nameor custom networks, and a named persistent volume.template.tomlgenerates a random 64-characterAPI_KEYand correctly maps the domain to port 42617.meta.jsonentry contains all required fields (id,name,version,description,logo,links,tags); the version0.6.4matches the Docker image tag exactly.strapientry frommeta.jsonis not a regression — the base branch contained a duplicatestrapientry, and thededupe-and-sort-meta.jsscript correctly removed the extra copy.${PROVIDER:-openrouter}default indocker-compose.ymlis redundant (template.toml already injects the value), andPROVIDERcould optionally be surfaced as a configurable template variable to make it easier for users to switch LLM providers at deploy time.Confidence Score: 5/5
Safe to merge — no functional or security issues; all template conventions are met.
The ZeroClaw template follows every hard requirement from AGENTS.md: correct Compose version, proper service naming, no forbidden directives, pinned image, no hardcoded secrets, and a valid meta.json entry. The only open items are two non-blocking P2 style suggestions. The Strapi removal is correct deduplication and not a regression.
No files require special attention.
Important Files Changed
Reviews (1): Last reviewed commit: "feat: add ZeroClaw template (v0.6.4)" | Re-trigger Greptile
(2/5) Greptile learns from your feedback when you react with thumbs up/down!
Context used:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.