feat: add PicoClaw personal AI agent stack#690
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: akurinnoy The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughTwo new files register the PicoClaw workspace stack: ChangesPicoClaw Stack
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
stacks/picoclaw/1.0.0/devfile.yaml (1)
37-47: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick winPin both container images to immutable refs.
ubi9-latestandpicoclaw:launcherare mutable, so stack1.0.0will 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
📒 Files selected for processing (2)
stacks/picoclaw/1.0.0/devfile.yamlstacks/picoclaw/stack.yaml
Add PicoClaw - an open-source personal AI assistant - as a devfile registry sample. Includes web UI on port 18800 and gateway on port 18790 with per-workspace storage. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Oleksii Kurinnyi <okurinny@redhat.com>
6240f65 to
ba8cfc9
Compare
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:
picoclaw-launcher) on port 18800 - configure agents, channels, API keysThe editor (VS Code, ttyd, etc.) is chosen separately in the dashboard and injected into the
toolscontainer.Related Issue(s)
N/A
Acceptance Criteria
Have you read the devfile registry contributing guide and followed its instructions?
Does this repository's tests pass with your changes?
Does any documentation need to be updated with your changes?
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
picoclaw onboardandpicoclaw statuscommands from the terminal/home/user/.picoclaw)How To Test
picoclaw onboardto configure an API keyNotes To Reviewer
HOME=/home/userset explicitly for OpenShift arbitrary UID compatibilitycookiesAuthEnabled: truefor authentication through the Che gatewaystarterProjects- the sample is a standalone agent, not a code projectSummary by CodeRabbit