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 web UI and gateway access through authenticated HTTPS endpoints.
  • Added persistent configuration storage for workspace settings.
  • Added commands to onboard, check status, and start the gateway.
  • Registered PicoClaw as an available stack, with version 1.0.0 as the default.
• Tests
  • Updated stack validation coverage to accommodate the new PicoClaw stack.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 770e800d-39cc-4f15-8ee5-89ad79213547

📥 Commits

Reviewing files that changed from the base of the PR and between 148b94f and 62079a1.

📒 Files selected for processing (4)

• .github/CODEOWNERS
• stacks/picoclaw/1.0.0/devfile.yaml
• stacks/picoclaw/stack.yaml
• tests/check_odov3.sh

🚧 Files skipped from review as they are similar to previous changes (3)

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

---

📝 Walkthrough

Walkthrough

Adds the PicoClaw stack registration, workspace devfile, container endpoints, persistent storage, executable commands, ownership entry, and Odo v3 test exclusion.

Changes

PicoClaw Stack

Layer / File(s)	Summary
Stack registration and ownership stacks/picoclaw/stack.yaml, .github/CODEOWNERS	Defines PicoClaw metadata, registers version 1.0.0 as the default, and assigns ownership for /stacks/picoclaw/.
Workspace components and storage stacks/picoclaw/1.0.0/devfile.yaml	Adds workspace metadata, the tools and picoclaw containers, authenticated HTTPS endpoints, launcher environment variables, persistent configuration storage, and a 1Gi volume.
Workspace commands and validation stacks/picoclaw/1.0.0/devfile.yaml, tests/check_odov3.sh	Adds onboard, status, and start-gateway commands and skips picoclaw in the Odo v3 test command.

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

Possibly related PRs

• devfile/registry#691: Adds an analogous AI agent runtime stack with related metadata, ownership, and Odo test-skip changes.

Suggested reviewers: johnmcollier, elsony, jdubrick, ibuziuk

🚥 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 identifies the addition of the PicoClaw personal AI agent stack, which is the main change.
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

[ibuziuk]

Suggested change

	schemaVersion: 2.2.2
	schemaVersion: 2.3.0

[michael-valdron]

@akurinnoy Tried this stack and lgtm, was able to launch the PicoClaw stack from my devfile registry build/deployment into DevSpaces.

To get around the odo test failures you'll need to add the stack to the skip list under tests/check_odov3.sh, see example.

[akurinnoy]

@michael-valdron thanks for testing! Added the odo v3 skip in 62079a1 and rebased to main.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akurinnoy, ibuziuk, michael-valdron

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [michael-valdron]

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