feat: add ZeroClaw AI agent runtime stack

[akurinnoy]

Description of Changes

Add ZeroClaw as a devfile registry sample - an open-source Rust-based AI agent runtime by ZeroClaw Labs.

The stack runs the ZeroClaw daemon in a sidecar container:

• Gateway server on port 42617 - webhooks, websockets, and web dashboard

The official ZeroClaw image is distroless, so we use a wrapper image (quay.io/che-incubator/zeroclaw-image) that adds a shell environment on UBI9-minimal. The wrapper is built from che-incubator/zeroclaw-image.

The editor (VS Code, ttyd, etc.) is chosen separately in the dashboard and injected into the tools container.

Related Issue(s)

N/A

Acceptance Criteria

• Contributing guide

Have you read the devfile registry contributing guide and followed its instructions?

• Test automation

Does this repository's tests pass with your changes?

• Documentation

Does any documentation need to be updated with your changes?

• Check Tools Provider

Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

Tests Performed

• Schema validation passed locally (bash tests/validate_devfile_schemas.sh)
• odo init passed locally with odo v3.16.1
• Started a workspace from the ZeroClaw sample on an OpenShift cluster (CRC, both amd64 and arm64)
• Verified the gateway/dashboard is accessible on port 42617
• Ran zeroclaw quickstart, zeroclaw status, and zeroclaw doctor from the terminal
• Confirmed config persists across workspace restarts (PVC at /home/user/.zeroclaw)

How To Test

1. Build a custom devfile registry image with this change
2. Deploy it to a Che/DevSpaces cluster
3. Create a workspace from the ZeroClaw sample
4. Open the gateway endpoint and run zeroclaw quickstart to create your first agent
5. Verify the dashboard works

Notes To Reviewer

• The official ZeroClaw image is distroless (no shell). This sample uses a wrapper image that adds bash and coreutils on UBI9-minimal
• The daemon is started via args: ["daemon", "--host", "0.0.0.0"] to bypass the wrapper's default entrypoint config step (already handled at image build time)
• The endpoint uses cookiesAuthEnabled: true for authentication through the Che gateway
• No starterProjects - the sample is a standalone agent runtime, not a code project

Summary by CodeRabbit

• New Features
  • Added a new ZeroClaw stack for launching the AI agent gateway/runtime.
  • Included a ready-to-use workspace setup with a tools container, a ZeroClaw service container, persistent storage, and a public HTTPS gateway endpoint.
  • Added built-in commands for quick start, status checks, and diagnostics.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: akurinnoy
Once this PR has been reviewed and has the lgtm label, please assign jdubrick for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

Warning

Review limit reached

@akurinnoy, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8c4137d4-8224-4451-b553-58436156e678

📥 Commits

Reviewing files that changed from the base of the PR and between 1e883b8 and 78b09bd.

📒 Files selected for processing (1)

• .github/CODEOWNERS

📝 Walkthrough

Walkthrough

Adds a new ZeroClaw stack to the devfile registry: a devfile.yaml defining stack metadata, tools and zeroclaw containers, a gateway endpoint, a PVC volume, and quickstart/status/doctor commands, plus a stack.yaml registering the stack with a default 1.0.0 version.

Changes

ZeroClaw Stack Addition

Layer / File(s)	Summary
Devfile metadata and runtime wiring stacks/zeroclaw/1.0.0/devfile.yaml	Defines stack metadata, tools and zeroclaw components, a gateway HTTPS endpoint on port 42617, a zeroclaw-data PVC, and quickstart/status/doctor exec commands.
Stack registry entry stacks/zeroclaw/stack.yaml	Registers the zeroclaw stack with display metadata and marks version 1.0.0 as default.

Estimated code review effort: 1 (Trivial) | ~4 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: adding the ZeroClaw AI agent runtime stack.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[michael-valdron]

Hello @akurinnoy,

Thanks for contributing this new stack entry, will you or the @devfile/che-team be owning this stack?

You'll need to add the official proposed owner(s) of this stack under https://github.com/devfile/registry/blob/main/.github/CODEOWNERS, for example:

# ZeroClaw stacks
/stacks/zeroclaw/ @akurinnoy @devfile/che-team

[akurinnoy]

Thanks for the review! Added the CODEOWNERS entry - I'll be the owner for now:

/stacks/zeroclaw/ @akurinnoy

[michael-valdron]

Hello @akurinnoy,

Tried testing spinning up this stack and I am encountering an "unknown error" (could not dig up the logs) that is happening with index-generator container. One clue I got is that its to do with the post-Start. I've included the error message down below as well as a screenshot of the DevSpace setup I'm using to test.