feat: add PicoClaw personal AI agent stack

[akurinnoy]

Description of Changes

Add PicoClaw as a devfile registry sample - an open-source personal AI assistant (Go, MIT).

The stack runs two services in a sidecar container:

• Web UI (picoclaw-launcher) on port 18800 - configure agents, channels, API keys
• Gateway HTTP server on port 18790 - webhook endpoint for chat channels

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

• Started a workspace from the PicoClaw sample on an OpenShift cluster (CRC)
• Verified the web UI is accessible on port 18800
• Verified the gateway endpoint is accessible on port 18790
• Ran picoclaw onboard and picoclaw status commands from the terminal
• Confirmed config persists across workspace restarts (PVC at /home/user/.picoclaw)

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 PicoClaw sample
4. Open the web UI endpoint and run picoclaw onboard to configure an API key
5. Verify the gateway and web UI endpoints work

Notes To Reviewer

• The image runs as non-root with HOME=/home/user set explicitly for OpenShift arbitrary UID compatibility
• Both endpoints use cookiesAuthEnabled: true for authentication through the Che gateway
• No starterProjects - the sample is a standalone agent, not a code project

Summary by CodeRabbit

• New Features
  • Added a new PicoClaw workspace stack with a ready-to-use development environment.
  • Included a launcher setup with web UI and gateway access, plus persistent configuration storage.
  • Added workspace commands to onboard, check status, and start the gateway.
  • Registered PicoClaw as a new available stack version and default option.

[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: 33e06f1d-f6b9-4343-9ec1-408144ab3d62

📥 Commits

Reviewing files that changed from the base of the PR and between 148b94f and 1c4e5ab.

📒 Files selected for processing (1)

• .github/CODEOWNERS

📝 Walkthrough

Walkthrough

Adds the PicoClaw stack registration, workspace devfile, container endpoints, persistent storage, executable commands, and CODEOWNERS entry.

Changes

PicoClaw Stack

Layer / File(s)	Summary
Stack registry entry stacks/picoclaw/stack.yaml, .github/CODEOWNERS	Defines stack metadata, registers version 1.0.0 as default, and assigns ownership for /stacks/picoclaw/.
Devfile metadata and storage config stacks/picoclaw/1.0.0/devfile.yaml	Adds workspace metadata, first-boot instructions, and the controller.devfile.io/storage-type attribute.
Container components and persistent volume stacks/picoclaw/1.0.0/devfile.yaml	Defines the tools and picoclaw containers, public HTTPS endpoints on ports 18800 and 18790, environment variables, persistent configuration storage, and a 1Gi PVC.
Devfile commands stacks/picoclaw/1.0.0/devfile.yaml	Adds onboard, status, and start-gateway commands targeting the picoclaw component with /home/user as the working directory.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: elsony, ibuziuk, johnmcollier

🚥 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 and concisely describes the main change: adding the PicoClaw personal AI agent 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

---

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

stacks/picoclaw/1.0.0/devfile.yaml (1)

37-47: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick win

Pin both container images to immutable refs.

ubi9-latest and picoclaw:launcher are mutable, so stack 1.0.0 will not be reproducible over time. Please use a versioned tag or digest for both images before publishing this registry version.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@stacks/picoclaw/1.0.0/devfile.yaml` around lines 37 - 47, Both container
images are using mutable tags, which makes this stack version non-reproducible
over time. Update the Devfile entries for the universal-developer-image and the
picoclaw launcher container to use immutable references such as a versioned tag
or digest, and make sure the container definitions in devfile.yaml reflect those
pinned image values before publishing 1.0.0.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@stacks/picoclaw/1.0.0/devfile.yaml`:
- Around line 65-72: The public webhook target defined under the gateway entry
is still requiring workspace cookie auth, which blocks third-party POSTs from
reaching the endpoint. Update the gateway attributes in the devfile so the
webhook path does not depend on cookiesAuthEnabled, keeping the rest of the
public exposure settings intact. Use the gateway service definition to locate
and adjust the auth-related attributes only.

---

Nitpick comments:
In `@stacks/picoclaw/1.0.0/devfile.yaml`:
- Around line 37-47: Both container images are using mutable tags, which makes
this stack version non-reproducible over time. Update the Devfile entries for
the universal-developer-image and the picoclaw launcher container to use
immutable references such as a versioned tag or digest, and make sure the
container definitions in devfile.yaml reflect those pinned image values before
publishing 1.0.0.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3226b987-86ad-4d07-866f-df9db5961b52

📥 Commits

Reviewing files that changed from the base of the PR and between 1c251d3 and 6240f65.

📒 Files selected for processing (2)

• stacks/picoclaw/1.0.0/devfile.yaml
• stacks/picoclaw/stack.yaml

[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:

# PicoClaw stacks
/stacks/picoclaw/ @akurinnoy @devfile/che-team

[akurinnoy]

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

/stacks/picoclaw/ @akurinnoy

[michael-valdron]

/retest