feat: add Hermes AI agent stack

[akurinnoy]

Description of Changes

Add Hermes Agent as a devfile registry sample - a self-improving AI agent with tool-calling and 50+ integrations by Nous Research.

The stack runs the Hermes runtime in a sidecar container:

• Dashboard web UI on port 9119
• Messaging gateway for Telegram, Discord, Slack, etc.

The official image uses s6-overlay which requires root, so the devfile bypasses it with a command/args override that sets up the environment and starts the dashboard directly.

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 Hermes sample on an OpenShift cluster (CRC, both amd64 and arm64)
• Verified the dashboard is accessible on port 9119
• Ran hermes setup, hermes status, and hermes doctor from the terminal
• Tested restart-dashboard command
• Confirmed config persists across workspace restarts (PVC at /opt/data)

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 Hermes sample
4. Open the dashboard endpoint and run hermes setup to configure your API key
5. Verify the dashboard and agent commands work

Notes To Reviewer

• The official image's s6-overlay entrypoint requires root, which is incompatible with OpenShift's arbitrary UID. The command/args override injects /etc/passwd for whoami, activates the venv, seeds config on first boot, and starts the dashboard with --insecure flag
• The dashboard starts with --insecure because there is no auth provider registered in the workspace context
• Uses docker.io/nousresearch/hermes-agent:v2026.6.5 directly from DockerHub
• The endpoint uses cookiesAuthEnabled: true for authentication through the Che gateway
• No starterProjects - the sample is a standalone agent, not a code project

[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 michael-valdron 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: 56 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: a095fd98-480d-4500-ad46-956e0fc7ffd9

📥 Commits

Reviewing files that changed from the base of the PR and between 1c251d3 and 05c447d.

📒 Files selected for processing (2)

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

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