<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Komodo on Derek's Guides</title><link>https://guides.derekleeds.cloud/tags/komodo/</link><description>Recent content in Komodo on Derek's Guides</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Apr 2026 16:42:20 -0500</lastBuildDate><atom:link href="https://guides.derekleeds.cloud/tags/komodo/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenClaw + Hermes: Multi-Agent Infrastructure</title><link>https://guides.derekleeds.cloud/docs/openclaw/openclaw-hermes-integration/</link><pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><guid>https://guides.derekleeds.cloud/docs/openclaw/openclaw-hermes-integration/</guid><description>&lt;p&gt;Connect OpenClaw (Clawdia) to Hermes Agent for delegating infrastructure tasks via HTTP API. This lets you manage Docker, Kubernetes, and GitOps operations through conversational commands.&lt;/p&gt;
&lt;h2 id="what-youll-learn"&gt;What You&amp;rsquo;ll Learn&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;When to use multi-agent architecture for infrastructure tasks&lt;/li&gt;
&lt;li&gt;How to connect OpenClaw to Hermes via HTTP API&lt;/li&gt;
&lt;li&gt;Configuring the Hermes integration skill&lt;/li&gt;
&lt;li&gt;Querying Docker, deploying stacks, and managing GitOps&lt;/li&gt;
&lt;li&gt;Security considerations for agent-to-agent communication&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="why-multi-agent"&gt;Why Multi-Agent?&lt;/h2&gt;
&lt;p&gt;Running everything in one agent creates a security problem. Infrastructure tasks need terminal and Docker access—capabilities you don&amp;rsquo;t want tied to your general-purpose assistant.&lt;/p&gt;</description></item></channel></rss>